Skip to content

Conversation

@aymeviviana
Copy link
Member

@aymeviviana aymeviviana commented Jan 27, 2026

Fixes #8461

What changes did you make?

  • Created new issue template for populating the github-handle variable with the github username

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

  • We need to populate the 'github-handle' variable with the correct GitHub username for each member of the leadership team. Eventually github-handle will replace the github and picture variables, reducing redundancy in the project file.

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

For Reviewers

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

No visual changes to the website.

@github-actions

This comment was marked as resolved.

@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 P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) time sensitive Needs to be worked on by a particular timeframe size: 1pt Can be done in 4-6 hours labels Jan 27, 2026
Copy link
Member

@daras-cu daras-cu left a comment

Choose a reason for hiding this comment

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

@aymeviviana great job on this issue! Your PR and branches are set up correctly and the template file looks good. Thanks for including the link for testing the template on your fork.

@myronchen-git
Copy link
Member

ETA: Jan 31
Availability: Jan 30, 7 AM - 10 AM; Jan 31, 7 AM - 10 AM

Copy link
Member

@myronchen-git myronchen-git left a comment

Choose a reason for hiding this comment

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

Good job on completing this.

I noticed the last action item in the issue wasn't checked off, and that the reason for the changes wasn't helpful to me, but those are nitpicks and aren't significant.

Other than those, everything is in order and done well. Instructions were well followed.

@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 Jan 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Complexity: Medium P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) 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 issue template for GFIs that populate 'github-handle' variable

3 participants