-
Notifications
You must be signed in to change notification settings - Fork 278
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
Enforce Push to Newly Created Branches, Not Main Branch #325
Comments
🙌 Thank you for bringing this issue to our attention! We appreciate your input and will investigate it as soon as possible ! |
You are not leveling up me 😢 |
also there are different format of footer in home, feature, team, contact tab? |
I will check it and update you, gimme a min |
@mansiruhil13 |
@mansiruhil13 Acc to gssoc rules and guidelines So everytime you merge a PR, it is better to ask the contributor who requested a PR to mention the issue number. This ensures whether they are assigned or creating a PR directly. @mansiruhil13 Have a look at this |
✅ This issue has been closed. Thank you for your contribution! If you have any further questions or issues, feel free to raise them, and we can discuss more! |
Problem:
Currently, contributors can push changes directly to the
main
branch. To maintain the stability of themain
branch and follow best practices, we want contributors to make their changes to a newly created branch and create a pull request for merging intomain
.Expected Behavior:
main
branch.main
.Suggested Solutions:
Implement a pre-push Git hook that checks if the push is being attempted on the
main
branch and stops the process with a reminder to create a new branch.e.g., some messages like "You are trying to push to the main branch. Please create a new branch and push your changes there."
The text was updated successfully, but these errors were encountered: