Update PR template to target staging branch

[JonDevOps]

edit this

• I have read w3Develops contribution guidelines.
• My pull request has a descriptive title (not a vague title like Update index.md)
• My pull request targets the production branch of production.
• None of my changes are plagiarized from another source without proper attribution.
• All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
• My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

[gemini-code-assist]

Summary of Changes

Hello @JonDevOps, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the project's pull request template to align with a revised branching strategy. The primary change directs contributors to submit their work against the staging branch, ensuring that new features and fixes are properly integrated and tested before reaching the production environment. This modification helps maintain the stability of the main production codebase.

Highlights

• PR Template Update: The pull request template has been updated to reflect a change in the recommended target branch for new contributions.
• Target Branch Change: The checklist item in the PR template now instructs contributors to target the staging branch instead of the production branch.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly updates the PR template to change the target branch from production to staging. The change is simple and effective. I've added one minor suggestion to improve the clarity of the template for future contributors. As a side note, please remember to fully edit the PR description in the future, removing placeholders like 'edit this' and filling in the issue number.

[gemini-code-assist]

For better clarity, especially for new contributors, consider explicitly mentioning that the branch is in the main repository. The previous text (... of production) was likely trying to achieve this, and adding of this repository would make the instruction clearer.

Suggested change

	- [ ] My pull request targets the `staging` branch.
	- [ ] My pull request targets the `staging` branch of this repository.

[RA9]

These are necessary changes. It would be nice if we can update the rules to not be the exact replica of freeCodeCamp