HfLA GitHub Actions

Workflows are yaml files

Supporting files can be

• js
• json
• md
• gitkeep

Template for GHA documentation

## Summary
### Scheduled
-
### Workflow
-
### Supporting Files/Folders
-
---
Back to [HfLA GitHub Actions](HfLA-GitHub-Actions)

Hack for LA's GHAs

add update label weekly

• Checks the in-progress column from the project board. Goes through each issue, and if there is an assignee, checks the timeline for the issue. If it is outdated, posts a comment to update the issue and ensures the label is changed to 'to update.' Else, change the label so it is 'updated'

github data

• Generates a new github-data.json and commits that to the repository

issue trigger

• Check if an issue has the three required labels. If not, add the 'missing' labels and post a comment about adding missing labels. If the issue has all, post a comment that congratulates and gives more details about the project board

lint-scss

• Checks and lints modified scss files in PRs

move closed issues

• Moves a closed issue into either the QA or Done column of the project board. If the issue has a “hard” label (Feature: Refactor CSS, Feature: Refactor HTML, Feature: Refactor JS / Liquid, Feature: Refactor GH), the issue is moved to the Done column. If the issue has no “hard” labels but does have an “override” label (role: front end), the issue is moved to the QA column. If the issue has no “hard” or “override” labels and does have a “soft” label (role: back end/devOps, Feature: Analytics), it is moved to Done. All other issues are moved to QA

pr instructions

---

• ✔️ Workflow: pull-request-trigger.yml

Pull request closed	An open script that could be triggered when a pull request is closed on the following branches 'gh-pages', 'feature-homepage-launch', 'feature-tech-dropdown'

• ✔️ Workflow: set-pr-labels.yaml
  • Supporting Files Folder: https://github.com/hackforla/website/tree/gh-pages/github-actions/trigger-pr

PR opened, PR edited	RegEx takes the issue number on the body of the PR, and uploads the results (including labels on the issue) into an artifact

• ✔️ Workflow: update-team-members.yml
  • Supporting Files Folder: https://github.com/hackforla/website/tree/gh-pages/github-actions/github-data

Scheduled to run at 11:00 every Thursday	Trim inactive members from the write team

• ✔️ Workflow: vrms-data.yml
  • Data: https://github.com/hackforla/website/blob/gh-pages/_data/external/vrms_data.json

Scheduled to run everyday at 10:00	Generates a new vrms_data.json and commits that to the repository

• ✔️ Workflow: wr-pr-instructions.yml
  • Supporting Files Folder: https://github.com/hackforla/website/tree/gh-pages/github-actions/pr-instructions

Workflow [Add Pull Request Instructions] completed	Leaves a comment on new PRs with a link to the relevant documentation for reviewing PRs and the command line instructions for pulling down a new branch for review.

• ✔️ Workflow: wr-pull-request-trigger.yml

Pull request closed	An open script that should house all the other scripts (workflows) that should be triggered when a pull request is closed

• ✔️ Workflow: wr-set-pr-labels.yaml
  • Supporting Files Folder: trigger-pr

Workflow [Set PR Labels] completed	This workflow is triggered when workflow [Set PR labels] is completed. Downloads artifact for the completed workflow. Then, gets the PR and issue number from the downloaded artifact and uses an API request to get the labels. Lastly, puts the same labels into the PR.

---

extra folders or files with unknown workflows

• Supporting Files Folder: trigger-schedule - folder has one file .gitkeep and its empty - The .gitkeep was likely added as a way of forcing git to track the new empty directory when the person who created the GHA began working on it. This is not a supported feature of git and now that there is content in the directory, there is no real need for the .gitkeep file The commit message for the .gitkeep file is just “Create directory for gha refactor”