GitLab fine-grained personal access tokens

Open Beginner friendly
#1,423 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
gitlab, go
Domain
authentication, documentation

Research direction

Check the existing documentation for GitLab personal access tokens in the project, likely in README or docs. Test if the new fine-grained tokens work with git-spice commands. If they work, update the docs; if not, investigate the authentication code in the Go source to see what changes are needed.

Written by the indexing model from the issue text.

Description

area/forge documentation

GitLab is switching to fine-grained personal access tokens, to limit vulnerabilities: https://docs.gitlab.com/auth/tokens/fine_grained_access_tokens/ & https://about.gitlab.com/blog/fine-grained-pats/

git-spice currently only has documentation for the old tokens, that are now called "Legacy tokens".

Supporting the new method would be nice. Not sure if that just needs a documentation change and the new tokens would already work or if code needs to change.

Dominant language
Go
Stars
768
Forks
72
Avg merge
1d 1h
Merged PRs (30d)
29

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from abhinav/git-spice

All issues in abhinav/git-spice

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.