RepoPalette

简体中文

RepoPalette generates a self-updating GitHub Profile language chart from your public repositories—with ten visual layouts, exact percentages, and files saved in your own repository.

RepoPalette reads your public repositories, creates an SVG in your Profile repository, and checks for changes every Monday.

One small file, one commit. No separate account, secret key, or image server to set up.

Quick start

Install with AI

If an AI coding agent can edit your Profile repository, paste this message into it:

Install RepoPalette in this GitHub Profile repository. Follow https://github.com/onovich/RepoPalette/blob/1ae03bf5436f1c0067640c87dec2f25cbe6eba96/docs/INSTALL_WITH_AI.md, use the defaults, and verify the first automatic run.

The guide tells the agent exactly what to change and what to leave alone. You do not need to explain GitHub Actions to it.

Install yourself

In your Profile repository (your-name/your-name), create .github/workflows/repopalette.yml and paste:

name: RepoPalette
on:
  workflow_dispatch:
  push:
    paths:
      - .github/workflows/repopalette.yml
  schedule:
    - cron: "17 3 * * 1"
permissions:
  contents: write
jobs:
  update:
    uses: onovich/RepoPalette/.github/workflows/profile.yml@3b0996b905fb3acd9049197cf5a1317b95224320 # v0.7.0

New to GitHub's file editor?

Open your Profile repository, choose Add file → Create new file, enter .github/workflows/repopalette.yml as the file name, paste the block above, then choose Commit changes.

Commit the file. That first commit starts RepoPalette automatically; when the Actions check turns green, the chart is already in your Profile README. It then checks every Monday. Actions → RepoPalette → Run workflow remains available whenever you want to refresh it manually.

The readable @v0.7.0 tag is also available. The full commit reference above is safer for a workflow that can write to your repository.

Why RepoPalette?

• More than a standard bar card. Ten layouts balance visual character with exact language names and percentages.
• Your Profile does not depend on a live image service. The generated chart belongs to your repository and remains visible if a later update fails.
• The result can be checked. A readable data file lists the repositories that were included or excluded instead of hiding the counting scope.
• The setup stays small. The short workflow handles generation, validation, README placement, and future updates.

Compare all layouts and themes in the gallery.

Common questions

I do not have a Profile repository yet. What should I do?

Create a public repository whose name exactly matches your GitHub username, initialize it with a README, then follow the Quick start above. GitHub will display that README on your Profile.

What gets counted?

Public repositories owned by your account. Forks are excluded, archived repositories are excluded by default, and percentages use GitHub's language byte counts. New public repositories are picked up on the next run. GitHub may pause schedules in a public repository after 60 days without repository activity; if that happens, re-enable the workflow in Actions and run it once. Details

Do I need to create a secret or personal token?

No. GitHub gives each run a temporary permission slip, then expires it. You do not create or store a long-lived private key, register another account, or deploy a server.

Why does the workflow need write permission?

Only to save the generated chart and data in your Profile repository and maintain its small marked section in README.md. It does not write to the repositories being measured.

Does it measure skill or detect AI-written code?

No. It reports language composition, not ability, time, quality, or authorship. An optional combined Manual/Vibe view is available only as a grouping you declare yourself.

Need more control?

The default is ribbon with the paper theme. See the gallery to choose a look, then use the advanced guide for themes, filters, titles, branding, the combined Manual/Vibe view, or the lower-level Action. The lower-level Action is available on GitHub Marketplace; most Profile users should use the Quick start because it also handles checkout, validation, README placement, and commits. Every input is listed in action.yml.

Contributors need Node.js 24 or newer and can run npm run check. See the changelog, product decisions, and MIT license.