Skip to content

fix(github-template): indentation #11667

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 29, 2025
Merged

fix(github-template): indentation #11667

merged 1 commit into from
Jul 29, 2025

Conversation

Parsaabasi
Copy link
Contributor

There was a wrong indentation in the previous change that caused discrepancy.
Here is the updated correct code.

@Parsaabasi Parsaabasi requested a review from pedrominatel as a code owner July 29, 2025 12:24
@Parsaabasi Parsaabasi self-assigned this Jul 29, 2025
Copy link
Contributor

Messages
📖 🎉 Good Job! All checks are passing!

👋 Hello Parsaabasi, we appreciate your contribution to this project!


📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

Click to see more instructions ...


This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...


We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 18daf31

@Parsaabasi Parsaabasi removed their assignment Jul 29, 2025
@lucasssvaz lucasssvaz added the Status: Pending Merge Pull Request is ready to be merged label Jul 29, 2025
@me-no-dev me-no-dev merged commit 4f0dd45 into master Jul 29, 2025
11 checks passed
@me-no-dev me-no-dev deleted the fix/indentation branch July 29, 2025 17:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Pending Merge Pull Request is ready to be merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants