Repository navigation
chore(ci): Enforce and guide PRs to target the dev branch - #796
lahirumaramba wants to merge 2 commits into
Conversation
Add a CI check to verify pull requests target the dev branch, and update PR template, CONTRIBUTING.md, and AGENTS.md to guide contributors to target dev.
Update branch references from master to main in PR template, CONTRIBUTING.md, AGENTS.md, and release.yml.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the repository documentation, including the pull request template, AGENTS.md, and CONTRIBUTING.md, to clarify that all development work and pull requests must target the dev branch instead of main (formerly master). It also updates references from master to main and updates the git clone instructions to target the dev branch. Feedback on these changes suggests using the /pull/new/dev URL format in CONTRIBUTING.md instead of /compare/dev... to maintain consistency with the previous URL structure.
|
|
||
| Sweet, we'd love to accept your contribution! | ||
| [Open a new pull request](https://github.com/firebase/firebase-admin-go/pull/new/master) and fill | ||
| [Open a new pull request](https://github.com/firebase/firebase-admin-go/compare/dev...) and fill |
There was a problem hiding this comment.
Using the /pull/new/dev endpoint is more consistent with the previous URL structure (/pull/new/master) and provides a cleaner, more direct interface for creating a pull request against the dev branch compared to the /compare/dev... syntax.
| [Open a new pull request](https://github.com/firebase/firebase-admin-go/compare/dev...) and fill | |
| [Open a new pull request](https://github.com/firebase/firebase-admin-go/pull/new/dev) and fill |
Add a CI check to verify pull requests target the
devbranch, and update PR template,CONTRIBUTING.md, andAGENTS.mdto guide contributors to targetdev.