Skip to content

Create an issue form template for Yearly Accomplishments - #8861

Open
MStoutTech wants to merge 1 commit into
hackforla:gh-pagesfrom
MStoutTech:yearly-accomplishments-form-template-8476
Open

MStoutTech wants to merge 1 commit into
hackforla:gh-pagesfrom
MStoutTech:yearly-accomplishments-form-template-8476

Conversation

@MStoutTech

@MStoutTech MStoutTech commented Nov 2, 2026 •

Copy link
Copy Markdown
Member

Fixes #8476

What changes did you make?

  • Created a new yml form template file in .github/ISSUE_TEMPLATE directory
  • Added project team drop down
  • Added hackforla.org website URL drop down
  • Added addition or revision drop down
  • Added years of accomplishment drop down for 2020-2026
  • Added text area for summary

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

  • This is a template to be able to create issues for adding or revising project team yearly accomplishments

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 before visuals

Visuals after changes are applied accomplishmentform

@github-actions github-actions Bot added role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Complexity: Medium time sensitive Needs to be worked on by a particular timeframe size: 1pt Can be done in 4-6 hours p-feature: accomplishments https://www.hackforla.org/about/#accomplishments HLC: M Homepage Launch Countdown Must Have labels Nov 2, 2026
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown

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 MStoutTech-yearly-accomplishments-form-template-8476 gh-pages
git pull https://github.com/MStoutTech/HackforLAwebsite.git yearly-accomplishments-form-template-8476

@yepezjuan
yepezjuan self-requested a review November 3, 2026 01:45
@yepezjuan

Copy link
Copy Markdown
Member

Availability: T, W 4-6pm
ETA, Wednesday, Nov. 4

@KyleA99

KyleA99 commented Nov 3, 2026

Copy link
Copy Markdown
Member

Availability: 11/2/26 7-9pm
ETA, 11/2/26 9 pm

@KyleA99 KyleA99 left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hello @MStoutTech great job!

  • The issue is correctly linked.
  • The PR and it's branches are structured correctly.
  • I previewed your yaml file in the browser and compared it to other .github/ISSUE_Template files and yours looked great. I did not see any deficiencies when comparing to the linked issue either.
  • All of the projects i prod are listed in your "Project Team" dropdown.
  • All of the links in the "Project URL on hackforla.org website" dropdown work.
  • The other dropdowns appear correct as well.
  • The comment is correctly left on the bottom of the issue form template.

Great work! Thank you for working on this!

@yepezjuan yepezjuan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hi @MStoutTech good work!

Your PR is titled and formatted. Did not notice and discrepancies in comparing your .yml file and the issue requirements. All drop down options seem to be in place as well as complete functional link navigation!

@github-project-automation github-project-automation Bot moved this from PR Needs review to PRs ✅ waiting for merge team in P: HfLA Website: Project Board Nov 3, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Complexity: Medium HLC: M Homepage Launch Countdown Must Have p-feature: accomplishments https://www.hackforla.org/about/#accomplishments role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours time sensitive Needs to be worked on by a particular timeframe

Projects

Status: PRs ✅ waiting for merge team

Development

Successfully merging this pull request may close these issues.

Create an issue form template for Yearly Accomplishments

3 participants