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

update pull_request_template with onboard notice #7803

Conversation

codyjohnsontx
Copy link
Member

@codyjohnsontx codyjohnsontx commented Dec 13, 2024

Fixes #7722

What changes did you make?

  • Add message at top of pull_request_template.md indicated in issue:

Why did you make the changes (we will use this info to test)?

  • Non-members have been creating PRs.
  • To solve issue, we add a this notice at the top of the PR template to notifiy developers they must complete onboarding prior to PRs

CodeQL Alerts

After the PR has been submitted and the resulting GitHub actions/checks have been completed, developers should check the PR for CodeQL alert annotations.

Check the PR's comments. If present on your PR, the CodeQL alert looks similar as shown

Screenshot 2024-10-28 154514

Please let us know that you have checked for CodeQL alerts. Please do not dismiss alerts.

  • I have checked this PR for CodeQL alerts and none were found.
  • I found CodeQL alert(s), and (select one):
    • I have resolved the CodeQL alert(s) as noted
    • I believe the CodeQL alert(s) is a false positive (Merge Team will evaluate)
    • I have followed the Instructions below, but I am still stuck (Merge Team will evaluate)
Instructions for resolving CodeQL alerts

If CodeQL alert/annotations appear, refer to How to Resolve CodeQL alerts.

In general, CodeQL alerts should be resolved prior to PR reviews and merging

Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)

Visuals before changes are applied
  • No visual changes to the website
Visuals after changes are applied
  • No visual changes to the website

Copy link

Want to review this pull request? Take a look at this documentation for a step by step guide!


From your project repository, check out a new branch and test the changes.

git checkout -b codyjohnsontx-update-pr-template-onboard-notice-7722 gh-pages
git pull https://github.com/codyjohnsontx/website.git update-pr-template-onboard-notice-7722

@github-actions github-actions bot added role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Complexity: Small Take this type of issues after the successful merge of your second good first issue size: 0.5pt Can be done in 3 hours or less labels Dec 13, 2024
@belunatic belunatic self-requested a review December 14, 2024 20:19
@belunatic
Copy link
Member

ETA: 12/17/24
Available: M-T 10-4PM

@DrAcula27 DrAcula27 self-requested a review December 16, 2024 18:39
Copy link
Member

@DrAcula27 DrAcula27 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@codyjohnsontx Great job on your Small Issue! Your code passed the ABC's, including:

Approved! 👍

@mchait18
Copy link
Member

Review ETA: end of 12/17/2024
Availability: 10-3 EST M-TH

Copy link
Member

@mchait18 mchait18 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for working on this issue, @codyjohnsontx !

You're doing these right:

  • The branch you made the change on is correct
  • The linked issue (original issue) number is included
  • The content required to add is accurate
  • The CodeQL Alerts are checked (check box above)
    Great job!

Things to review:

  • Not all items on the original issue are checked

Copy link
Member

@belunatic belunatic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@codyjohnsontx great job, a fantastic work

  • The branch name is on point
  • great job and letting us know what changed
  • The links works
  • Everything is checked on the original issue

Way to end the year with a bang! lol!

Thanks again for you hardwork.

@siyunfeng siyunfeng merged commit 3787e1b into hackforla:gh-pages Dec 18, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less
Projects
Development

Successfully merging this pull request may close these issues.

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