Commits on Sep 19, 2024

1. Update workflows to use actions that don't need organization secrets (#… …

   …9126)
   
   * Update workflows to use actions that don't need organization secrets
   
   Each repository can only have 100 organization secrets and there are now more than 100 in our organization which causes inconsistent behavior.
   
   Some repositories don't have the secrets they need assigned.
   
   These composite actions use secrets stored in Vault that are available to all repositories.
   
   - `publish-technical-documentation-next.yml` has been tested with https://github.com/grafana/writers-toolkit/blob/main/.github/workflows/publish-technical-documentation.yml.
   - `publish-technical-documentation-release.yml` has been tested with https://github.com/grafana/backend-enterprise/blob/gem-release-2.13/.github/workflows/publish-technical-documentation-release.yml.
   
   There is some copy-paste involved in the creation of these workflows. Please check:
   
   For `publish-technical-documentation-next.yml`:
   
   - [ ] The `on.push` `branches` and `paths` filters are correct for your repository.
   - [ ] The `jobs.sync.if` repository matches your repository.
   - [ ] The `jobs.sync.steps[1].with.website_directory` matches the directory you publish to in the website repository.
   
   For `publish-technical-documentation-release.yml`:
   
   - [ ] The `on.push` `branches`, `tags`, and `paths` filters are correct for your repository.
   - [ ] The `jobs.sync.if` repository matches your repository.
   - [ ] The `jobs.sync.steps[1].with.release_tag_regexp` regular expression matches your tags and captures major, minor, and patch versions from those tags.
   - [ ] The `jobs.sync.steps[1].with.release_branch_regexp` regular expression matches your release branch names and captures major and minor versions from those branch names.
   - [ ] The `jobs.sync.steps[1].with.release_branch_with_patch_regexp` regular expression matches your release branch names if they were to include a patch version, and that it would capture major, minor, and patch versions from those branch names.
   - [ ] The `jobs.sync.steps[1].with.website_directory` matches the directory you publish to in the website repository.
   
   We'll also need to backport this to any branches where you are maintaining documentation that you want synced to the website.
   
   Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
   
   * Fix repo
   
   * Add explanatory comments
   
   ---------
   
   Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
   (cherry picked from commit bbd2a24)

   

   jdbaldry authored and grafanabot committed Sep 19, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 0641a70
   • Browse repository at this point

   Copy the full SHA

   0641a70 View commit details

   Browse the repository at this point in the history