Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Error: in PR reviewdog token error

Open
#677 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
github, vim
Domain
ci-cd

Research direction

Start with the Travis CI job linked in the issue and inspect scripts/run-lint-on-ci.sh, especially the reviewdog invocation. Determine why the GitHub access token is sometimes unavailable; done means the lint job can run reviewdog without the reported 401 token error.

Written by the indexing model from the issue text.

Description

This problem sometimes happen. (not always)

see
https://travis-ci.org/vim-jp/vital.vim/jobs/554280167#L806-L809

# Run reviewdog.
reviewdog -reporter=github-pr-check
reviewdog: status=401: The access token not provided. Get token from https://reviewdog.app/gh/vim-jp/vital.vim
The command "if [[ "${RUN_LINT}" == "true" ]] ; then bash scripts/run-lint-on-ci.sh ; fi" exited with 1.

Is this well-known problem?

Dominant language
Vim Script
Stars
586
Forks
64
Avg merge
9h 24m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 vim-jp/vital.vim

All issues in vim-jp/vital.vim

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.