mitigram/git reset
Will '--hard' reset a branch to the content of another branch and '--force' push it to the origin. By default, the source branch will be the default branch at GitHub and the destination branch the branch where this action is run from. Note that orphane workflows, e.g. when run from a 'schedule' are anchored to the default branch. This action supposes that you have already a local copy of the repository, i.e. that you already have run `actions/checkout@v2` at a prior step.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| source | Name of the source branch, defaults to the default branch for the current repository. | yes | ${{ github.event.repository.default_branch }} |
| destination | Name of the destination branch which content will be overriden with the content of the source branch. Default to the branch where this action is run in. | yes | ${{ github.ref_name }} |
| dry-run | when set to false, this will prevent force pushing the reseted branch, instead a message will be printed out. | no | false |
Outputs
no outputs