Comments (5)
@macmiranda The default GITHUB_TOKEN
used to push the commit has limited permissions. It does not allow to make changes to workflow files.
As a workaround, you can use a Personal Access Token with the workflow
scope instead of the default GITHUB_TOKEN
as the token input for the checkout action step.
from backport-action.
Yes, the workaround worked fine. I don't like using PATs though, especially the classic ones, they are overly powerful. It also doesn't make sense to have a PAT for a repo under an organization because the person could leave the company at any time and then the PAT is worthless (we use an automation user for that, but it takes a paid seat of the organization 😞)
Anyway, cool GitHub action. Thanks for sharing it.
Looking forward to a solution for #39
It would also be cool if there was an option to merge the backported commit directly, without the PR.
from backport-action.
Hey @korthout hitting the exact same issue. Would you know what's the actual reason for this?
from backport-action.
Thanks. It's a shame we can't just add the capability to the runner token
from backport-action.
Absolutely agree. I guess GitHub sees a vulnerability, but it doesn't really apply to backport-action as it only deals with merged pull requests.
Let me know whether the workaround works for you, and I'd love to hear any other feedback on the action by the way. 🙇
from backport-action.
Related Issues (20)
- Publish action on marketplace HOT 3
- Unable to eat dogfood HOT 1
- Automate release process
- Document action outputs
- [Feature Request] Support auto-deletion for branches if the backport PR is closed HOT 1
- Feature request: allow specifying mainline HOT 9
- PR commits are cherry-picked instead of the squashed commit HOT 8
- Feature request : backport to all open feature branches HOT 8
- Use PAT in eat-your-own-dogfood workflow
- Support glob patterns in `target_branches` input
- Support skipping merge commits HOT 3
- PRs created by backport-action should trigger the CI HOT 1
- ability to backport a PR to any repo, not necessarily a fork HOT 3
- support backport, committing conflicts HOT 4
- Instructions for manually cherry-picking are incorrect as they do not skip merge commits HOT 2
- Get The successful PR numbers as an output of the action HOT 1
- Improve the error messages
- Conflict resolution `draft_commit_conflicts` provides incorrect instructions
- Conflict resolve suggestion doesn't fetch commits to cherry-pick HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from backport-action.