Create Project Automation Shared Workflows

[jarmak-nv]

Closes #163

This PR creates 5 new reusable workflows, all for project automation tasks.

• project-get-item-id.yaml

  • All project automation workflows need to call this once, projects use a custom ID for items within them rather than the global node id of the item. This returns the ID needed for downstream automations

• project-get-set-iteration-field.yaml

  • This finds the current iteration and returns it
  • if UPDATE_ITEM is set to true, it sets the field for the item to the current iteration as well
  • if UPDATE_LINKED_ISSUES is set to true, it also sets the same iteration to linked issues

• project-get-set-single-select-field.yaml

  • This finds a specific OptionId for a provided single select value and returns it
  • if UPDATE_ITEM is set to true, it sets the field for the item to the given value as well
  • if UPDATE_LINKED_ISSUES is set to true, it also sets the same field to linked issues

• project-set-text-date-numeric-field.yaml

  • These three all follow similar usage patterns in graphQL so they're combined
  • Currently, these only set values, but if given a necessary usecase we could switch to a get-set as well
  • if UPDATE_LINKED_ISSUES is set to true, it also sets the same field to linked issues

• project-update-linked-issues.yaml

  • The get-set/set workflows all call this workflow when UPDATE_LINKED_ISSUES is true

These workflows have all been tested:

• On this PR
• Successful run link is here
• Caller Workflow is here
  • You may note how there are hard-coded graphQL IDs for project fields in the caller workflow
    • This is done because otherwise we need to constantly re-query the fields and I want to minimize querying to prevent any possible graphQL API rate limiting against the token. Per GitHub these are static values so we shouldn't get caught out by changing values.

TODO BEFORE MERGE

Currently all of the reusable workflows have the secret set to PROJECT_MANAGEMENT_SECRET, this needs to be changed to ADD_TO_PROJECT_GITHUB_TOKEN which is a token scoped specifically for project-related tasks.

[bdice]

I might be missing something in the terminology here. What is an iteration field?

[jarmak-nv]

I might be missing something in the terminology here. What is an iteration field?

Docs on iteration fields

But regardless of docs, the most common iteration field is a sprint field. They can also represent releases, or really any block of time between two dates depending on the level of maintenance people want to apply to the field since in the project you can modify the start/end dates beyond the automatically provided "every X weeks"

[ajschmidt8]

LGTM.

Btw, you can also use the github-script action for making GitHub API calls.

github-script is able to make GraphQL calls and also has the benefit of supporting retries to avoid random transient networking issues:

• https://github.com/actions/github-script?tab=readme-ov-file#run-custom-graphql-queries
• https://github.com/actions/github-script?tab=readme-ov-file#retries