Update PR Template with adding a notice of completing onboarding before creating a PR

Overview

We have observed non-members creating PRs. To solve this, we will add a notice to the top of the PR template notifying developers that they must complete onboarding before creating a PR.

Action Items

[ ] Open the file .github/pull_request_template.md in your IDE

[ ] Add the following text:

Please note: You must be a member of the HFLA website team in order to create pull requests. Please see our page on how to join us as a member at HFLA: https://www.hackforla.org/getting-started. Delete this message if you joined this team via onboarding.

above

Fixes #replace_this_text_with_the_issue_number

[ ] Push your issue branch to your fork of the website repository, as described in Section 3.1.a of CONTRIBUTING doc, for example: git push --set-upstream origin test-update-labels-1234
[ ] Complete the Pull Request process by visiting the URL from the push command
[ ] Submit PR
[ ] Follow these steps to test the updated PR template:
- [ ] Navigate to the Pull Requests tab on your branch for this PR, and click the New Pull Request button
- [ ] Make sure you are on the right branch, and click the Create pull request button
- [ ] Verify the appearance of the updated PR template, and compare it with .github/pull_request_template.md
- [ ] Close the Create pull request page

Resources/Instructions

For QA to validate change: https://github.com/hackforla/website/blob/gh-pages/.github/pull_request_template.md?plain=1
This issue was initiated by #6058

Hi @siyunfeng.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

Complexity, Role, Feature, Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards. To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

hackforla / website