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

Project Board Migration: refactoring of "Pull Request Trigger" workflow #6997

Closed
4 of 5 tasks
Tracked by #6993
t-will-gillis opened this issue Jun 12, 2024 · 2 comments · Fixed by #7054
Closed
4 of 5 tasks
Tracked by #6993

Project Board Migration: refactoring of "Pull Request Trigger" workflow #6997

t-will-gillis opened this issue Jun 12, 2024 · 2 comments · Fixed by #7054
Assignees
Labels
Complexity: Large Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms role: back end/devOps Tasks for back-end developers size: 8pt Can be done in 31-48 hours

Comments

@t-will-gillis
Copy link
Member

t-will-gillis commented Jun 12, 2024

Dependency

Overview

Many of our workflows need to be refactored due to the forced migration from the Project Board (classic) to the Project Board- Beta (PBB). This issue addresses changes that we need to make in order to ensure that our "Pull Request Trigger" workflow works as it did previously.

Action Items

  • In pull-request-trigger.yml remove the entirety of the job "Move-New-PRS-To-Project-Board", that is lines 14 through 26. (The "Default workflows" will do this now.)
  • In same file, delete the remaining jobs. Currently, the workflow removes PRs from the board that either are or are not merged. The PBB "Default workflows" can auto-archive PRs that match this description. Post-migration, we will decide whether these PRs need to be auto-removed as well.
  • Leave "Hello World" as a placeholder.

Post migration issues needed:

  • Confirm: Need issue for action that will remove merged && unmerged + closed PRs from Project Board- in the new PBB these PRs are auto-archived but still exist in the project.

Resources/Instructions

@t-will-gillis t-will-gillis added role: back end/devOps Tasks for back-end developers Complexity: Large Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms size: 8pt Can be done in 31-48 hours Draft Issue is still in the process of being created labels Jun 12, 2024
@t-will-gillis t-will-gillis self-assigned this Jun 12, 2024

This comment was marked as resolved.

@t-will-gillis t-will-gillis added the Dependency An issue is blocking the completion or starting of another issue label Jun 12, 2024
@ExperimentsInHonesty ExperimentsInHonesty added role: back end role: back end/devOps Tasks for back-end developers and removed role: back end/devOps Tasks for back-end developers labels Jun 18, 2024
@t-will-gillis t-will-gillis removed the Draft Issue is still in the process of being created label Jun 20, 2024
@ExperimentsInHonesty ExperimentsInHonesty removed the Dependency An issue is blocking the completion or starting of another issue label Jun 23, 2024
@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jun 23, 2024

  • Need to move after pr actions to the epic
- [ ] Post migration issues needed after #6997 is closed
   - [ ] Confirm: Need issue for action that will remove merged && unmerged + closed PRs from Project Board- in the new PBB these PRs are auto-archived but still exist in the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms role: back end/devOps Tasks for back-end developers size: 8pt Can be done in 31-48 hours
Development

Successfully merging a pull request may close this issue.

2 participants