Will Gillis

Hi @roslynwythe and @iancooperman because of another automation's requirements, the `HACKFORLA_ADMIN_TOKEN` also needed the "repo" scope. It now has the following scopes so I believe it will work for this...

@ExperimentsInHonesty your thoughts? Following is one way to find a project start date using a GitHub Action: - The GitHub REST API (version 2022-11-18) to access information about a project's...

Testing in my repo: Does a github action that moves an issue from QA on close to the done column (designed for the old board to move an issue to...

@ExperimentsInHonesty 3 issues opened, and 3 corresponding PRs generated before Migration: - 1 `role: back end/devOps`, - 1 `role: front end`, - 1 `feature: refactor GHAs` After migration, I reviewed,...

@ExperimentsInHonesty Updates: in the new Project Board / Project Board Beta's "Default workflows", there are options for adding new issues and new PRs to the Board- This makes much of...

# Affected workflows ## Found so far | Issue Workflow | Step | Problem | If It Isn't Fixed | |:--:|:--:|:--:|:--:| | #6996 [issue-trigger.yml](https://github.com/hackforla/website/blob/gh-pages/.github/workflows/issue-trigger.yml) | "Add-Issue-To-Project-Board" | _OK if code...

Additional notes: We need to revise the wiki docs including: - [x] revise https://github.com/hackforla/website/issues/6537#issuecomment-2041147335

For future discussion: Since we are talking about linters, [here are comments](https://github.com/hackforla/website/issues/5048#issuecomment-2106039937) regarding the `lint-scss.yml` workflow and the `github/super-linter`

- Removing `Dependency`, adding `Ready for Dev Lead`, and moving to "New Issue Approval" due to merging of #4427

Hey @irais-valenzuela Since this is for the internal "Projects-Check" page, my thought is that the focus should be geared towards explaining the technical purpose more so than UI