Skip to content
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

Closed
poorvikaa08 opened this issue Oct 6, 2024 · 7 comments
Closed

Enforce Push to Newly Created Branches, Not Main Branch #325

poorvikaa08 opened this issue Oct 6, 2024 · 7 comments

Comments

@poorvikaa08
Copy link
Contributor

Problem:
Currently, contributors can push changes directly to the main branch. To maintain the stability of the main branch and follow best practices, we want contributors to make their changes to a newly created branch and create a pull request for merging into main.

Expected Behavior:

  • Contributors should be reminded or restricted from pushing directly to the main branch.
  • All changes should be pushed to a feature branch (i.e., a newly created branch named after the feature/issue).
  • A pull request (PR) should be created to merge changes from the feature branch into 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."

Copy link

github-actions bot commented Oct 6, 2024

🙌 Thank you for bringing this issue to our attention! We appreciate your input and will investigate it as soon as possible !

@poorvikaa08
Copy link
Contributor Author

poorvikaa08 commented Oct 6, 2024

You are not leveling up me 😢

@vimistify
Copy link
Owner

vimistify commented Oct 6, 2024

also there are different format of footer in home, feature, team, contact tab?

@poorvikaa08
Copy link
Contributor Author

also there are different format of FAQ in home, feature, team, contact tab?

I will check it and update you, gimme a min

@poorvikaa08
Copy link
Contributor Author

@mansiruhil13
FAQ sections have been removed according to latest updates

@poorvikaa08
Copy link
Contributor Author

@mansiruhil13
Also I have noticed that few of the contributors are directly working on the issue without getting assign and raising them.

Acc to gssoc rules and guidelines
Those PRs must be rejected.

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
Thankyou

Copy link

github-actions bot commented Oct 9, 2024

✅ 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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants