Azure
[Feature Request]: Implement an alternative solution to the current GitHub readme update approach
Description
Description
Currentlty, several files in the repository (e.g., ./README.md, ./modules/README.md) and others in the docs are maintained automatically using an automated pipeline.
The challenge: In order to update these files following a pull request, the operating principal must have permissions to push to main. This is, in general, not ideal as this means at least one user must have permissions to bypass the default branching policies.
To this end, we should consider implementing an alternative solution that uses for example self-approved pull requests instead.
Acceptance criteria
A more secure solution that is not dependent on PAT tokens is implemented and operational.
Let's revisit this item to collect some inputs from contributors such as @jtracey93 & @matt-FFFFFF.
Two options as I see it:
- The auto doc generation is run by the developer, the pipeline checks that it has been run and fails if not.
- Use a GH app to push to the repo and create PR. However strongly opposed to auto-approval. 1ES does not like it either.
Someone can volunteer to implement this and then present the solution for review.
