Skip to content

Git widget

Your open pull requests, or your contribution graph, from GitHub, Gitea, Forgejo or GitLab. Pick one with the View setting. Both come in every size.

GitLab shows merge requests only. It has no API for its contribution graph.

Point at a day on the contribution graph to see its date and count. The card follows the light and dark theme.

Pull requests
Contributions
The pull requests shown are made up.

Settings

  • ServiceGitHub, Gitea, Forgejo or GitLab.
  • Server URLGitea, Forgejo and GitLab only. The address of your server. An address without http:// or https:// uses https.
  • ViewPull Requests or Contributions. Not shown for GitLab.
  • UsernameThe account to read.
  • Personal Access TokenSee below.
  • Link URLWhere the widget links. Leave blank to open your profile.Optional
  • Pull request filtersPull requests only. Created, Assigned, Mentioned or Review requested. A pull request must match every filter you pick. GitLab names it Merge request filters and has no Mentioned.

On Gitea and Forgejo, the filters read the account that owns the token.

Pull requests are listed by last update. Gitea lists the newest first.

GitHub. Create a classic token at GitHub, Personal access tokens with the repo and read:user scopes. For public repositories only, public_repo and read:user are enough. A fine-grained token with the same read access also works.

Gitea and Forgejo. Create an access token with the read:user and read:issue scopes.

GitLab. Create a fine-grained personal access token with the Merge Request permission set to Read, or a legacy personal access token with the read_api scope.

Key rejected on the widget means the token is wrong, expired or missing a scope.