GitHub
Aktivnost u public/private repozitorijumima pored ostalih brojki projekta.
What you get
Section titled “What you get”| Metric | How it’s counted | Period value |
|---|---|---|
| Commits | Commits on the default branch, by commit date | Sum of the days |
| PRs merged | Pull requests merged, by merge date | Sum of the days |
| Lines changed | Lines added plus lines removed, leaving out merge commits | Sum of the days |
| Open issues | Issues open right now (pull requests excluded) | Latest observation |
Releases → events.
UTC dani. Open issues zahtevaju uključene issues na repo-u.
Step 1: Create a token
Section titled “Step 1: Create a token”Fine-grained personal access token — read-only, izabrani repozitorijumi.
-
GitHub Settings → Developer settings → Personal access tokens → Fine-grained tokens → Generate new token.
-
Ime „Metribay“, istek.
-
Resource owner — ti ili org.
-
Repository access → Only select repositories.
-
Permissions → Repository permissions Read-only:
- Contents
- Issues
- Pull requests
Metadata read-only auto.
-
Generate token — kopiraj jednom.
Org može tražiti odobrenje tokena od owner-a.
Step 2: Connect it in Metribay
Section titled “Step 2: Connect it in Metribay”-
Add data source → GitHub.
-
Connect an account with your own credentials → Personal access token.
-
Save account and continue.
-
Repository sa liste.
-
Add and start import.
Enter the repository by hand
Section titled “Enter the repository by hand”Enter it manually — owner/repository, npr. octocat/hello-world.
Other ways to sign in
Section titled “Other ways to sign in”Classic personal access token. Public repos: bez scope-ova. Private: repo scope (i write) — bolje fine-grained.
GitHub App. Use a GitHub App instead: Client Id, Installation Id, GitHub App private key (PEM). Read-only Contents, Issues, Pull requests. Repo ručno — nema liste.
Good to know
Section titled “Good to know”- Prvi importi spori na zauzetim repo-ima — ceo history window.
- Svaki sync ponovo čita ceo history window — kasni merge na default branch.
- Veoma veliki repo + dug window može udariti GitHub limite — kraći window.