mathieudutour / mathieudutour/github-tag-action
PAT setup for github-tag-action
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 733
- Forks
- 227
- PR merge metrics
- No merged PRs in 30d
Description
Hi guys, I'm working in a repository in an organization. I'm using a new PAT (Fine-grained Personal Access Token). I wonder to know which permissions would be set for github-tag-action working properly.
I've set it like this:
But it seems action can't read the previous tags: (it always says dev@0.0.0 even though we already had dev@0.1.0)
Did anyone experience the same context? please help me with this
Contributor guide
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 by reviewing github-tag-action's documentation and configuration for fine-grained PAT permissions, then reproduce the reported case in an organization repository with an existing dev@0.1.0 tag. Done means identifying the required permissions or confirming a specific action defect and documenting why the previous tag is not read.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions, typescript
- Domain
- ci-cd, devops, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100