Allow force push
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
with regards to #945
The solution in that issue doesn't work if you require passing checks before merge.
On both normal accounts and enterprise accounts you can use [wow-actions/use-app-token@v1](https://github.com/wow-actions/use-app-token) to create a surrogate bot and let that generate a token which causes the action to run in the context of that bot.
This is important because:
- in enterprise organisations, you can just enable "allow bots or persons to by pass restrictions" in the branch protection rule by listing the user or bot.
- in a normal account, you can only list a user or bot as being allowed to force push. (the
section "allow user or bot to bypass restrictions" is absent)
**Describe the solution you'd like**
- configuration to allow force push:
- git-tags
- changelog
**Describe alternatives you've considered**
🤷🏻
**Additional context**
Not everyone can afford enterprise accounts.
Contributor guide
No contributing guide indexed for this repository
Research direction
No repository file or test is named. Trace the configuration for git-tags and changelog, then review issue #945 and the referenced use-app-token action. Done means those release operations can force-push through the stated branch restrictions using the configured bot or user.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100