콘텐츠로 이동

Using the All Contributors CLI

All Contributors command line interface commands

섹션 제목: “All Contributors command line interface commands”

You will mostly use four commands:

Command What it does
init Prepare a project to use the CLI
add Add a contributor or update their contribution types
check Find contributors who are not yet acknowledged
generate Regenerate the contributor tables and badge

You can run all-contributors init when you first start using the All Contributors CLI. This command asks you a few questions and then sets up the project to support All Contributors.

터미널 창
npx all-contributors init

The setup includes creating:

  • an .all-contributorsrc configuration file and
  • a contributor table in the files you specify.

The default file for the contributor table is your README.md.

Use the add command to add:

  • new contributors to your project, or
  • new ways in which they have contributed.

If you run add without a username, the CLI asks who to add and which contribution types to record.

터미널 창
npx all-contributors add
? What is the contributor's GitHub username? lwasser
? What are the contribution types? 💻 Code, 📖 Documentation

If you pass a username and one or more contribution types, the CLI adds that person without those prompts. For instance, someone may already be credited for code, and you later want to credit a documentation pull request too. The contributor is updated in your configuration file, and the contributors file is updated just as if you used the generate command.

터미널 창
# Add new contributor <username>, who made a contribution of type <contribution>
npx all-contributors add <username> <contribution>
# Example:
npx all-contributors add jfmengels code,doc

Where username is the user’s GitHub or Gitlab username, and contribution is a ,-separated list of contributions. See the Emoji Key (Contribution Types Reference) for a list of valid contribution types.

Use check to compare people who have commits on GitHub or GitLab with the ones credited in your .all-contributorsrc file.

The command prints two lists when it finds a mismatch: people who have commits but are missing from .all-contributorsrc, and people credited for code or tests who have no matching commits.

Missing contributors in .all-contributorsrc:
octocat
Unknown contributors found in .all-contributorsrc:
ghost
터미널 창
npx all-contributors check

Use generate to read the contributors list from your .all-contributorsrc file and update the contributor tables specified by the files key.

터미널 창
npx all-contributors generate

코맨드가 목록을 갱신하기 위해서는 해당 파일에서 다음 태그를 찾을 수 있어야 합니다.

<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
<!-- ALL-CONTRIBUTORS-LIST:END -->

또한 배지를 업데이트하기 위해서는 다음 태그를 찾을 수 있어야 합니다.

<!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->
<!-- ALL-CONTRIBUTORS-BADGE:END -->

In some cases you may see the error message GitHub API rate limit exceeded for xxx. You may need to set an environment variable named PRIVATE_TOKEN to circumvent this GitHub rate limit.

Private Token은 GitHub API에서 인증을 위해 사용하는 개인 액세스 토큰(Personal Access Token, PAT)입니다.

Please note that if you are using a self-hosted GitLab instance, If you are using a private repository, a self-hosted GitLab instance, or encounter rate limits on GitLab.com, set an environment variable named PRIVATE_TOKEN.

터미널 창
# Linux에서 개인 토큰 설정
export PRIVATE_TOKEN=your_private_token
# Windows에서 개인 토큰 설정
set PRIVATE_TOKEN=your_private_token