semantic-release / semantic-release/git
Unable to create Release on Azure Devops
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 339
- Forks
- 75
- Avg merge
- 5h 15m
- Merged PRs (30d)
- 6
Description
As per the Azure Devops Docs regarding Branch Policies
A branch that has required policies configured can't be deleted, and requires pull requests (PRs) for all changes.
I have tried enabling
- Bypass policies for the Build Service
- Also given force push permissions
But I am getting the following response
! [remote rejected] HEAD -> main (TF402455: Pushes to this branch are not permitted; you must use a pull request to update this branch.)
shortMessage: 'Command failed with exit code 1: git push --tags https://dev.azure.com/**** HEAD:main',
command: 'git push --tags https://dev.azure.com/**** HEAD:main',
escapedCommand: 'git push --tags "[https://dev.azure.com/****"
exitCode: 1,
signal: undefined,
signalDescription: undefined,
stdout: '',
' ! [remote rejected] HEAD -> main (TF402455: Pushes to this branch are not permitted; you must use a pull request to update this branch.)\n' +
"error: failed to push some refs to '[https://dev.azure.com/*******"]
failed: true,
timedOut: false,
isCanceled: false,
killed: false,
pluginName: '@semantic-release/git'
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported @semantic-release/git command, git push --tags ... HEAD:main, and the Azure DevOps TF402455 response. Compare the documented branch-policy behavior with the reported permissions, then determine whether the issue requires a plugin change or an Azure DevOps configuration/documentation clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, git, javascript
- Domain
- devops, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100