Badge SVG token scope

Open
#958 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
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet

Research direction

Review the linked private-repository badge documentation and the README usage shown in the issue. Determine the token's scope and consequences of exposure; done means the issue has a clear, documented answer or identifies the required documentation change.

Written by the indexing model from the issue text.

Description

As mentioned in https://docs.codecov.com/docs/status-badges#badges-for-private-repositories - private repo badges need to include the token query parameter e.g. https://codecov.io/github/codecov/gazebo/graph/badge.svg?token=ASDF123456

Since badge URLs get pasted in READMEs, they may get accidentally published when making the repo public.

Could you confirm what's the scope of this token and what are the consequences of leaking it?

Dominant language
No language data
Stars
52
Forks
25
PR merge metrics
No merged PRs in 30d

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 codecov/feedback

All issues in codecov/feedback

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.