Product

Everything Govlin does

Govlin Desktop has six sections, each answering one question, and Ask on every screen. This is what you will find in the app today.

01Action Center

What needs my attention?

The one home for everyone: an inbox of problems, each cause once, with what is happening, why it matters and the action that fixes it.

  • Problems such as changes Govlin could not link to a ticket, no CI result in the window, integrations that send no data or an unsaved organization profile.
  • Each problem shows the evidence behind it: coverage, the affected changes and the pipeline runs.
  • "What Govlin receives today": one line per integration, so you see what is connected and what is missing.
  • A status line (Setup · Release · Evidence) and the real time the data was loaded.

Who: Everyone. Its content adapts to your permissions.

02Workspace

What am I changing?

Prepare and send the current change without leaving Govlin: files, diff, branch, commit, push and a terminal.

  • The flow of the change, Ticket → Branch → Stage → Commit → Push / PR → CI pipeline, with the next local step.
  • Change impact, computed on your machine: size and review time, sensitive areas (database, CI/CD, auth, infrastructure, secrets, dependencies), hotspots and files that usually change together but are missing.
  • Ready to push: every commit names a ticket, the branch carries one and it is up to date with its base.
  • Rule feedback before the push, and the state of your last push. The change impact analysis never leaves your computer.

Who: Anyone with local Git access.

03Releases

Can this ship?

A release is a repository plus an immutable commit. Govlin computes its state in every environment and keeps human decisions apart.

  • A release appears when the CI asks for a deployment authorization, a decision is recorded or you evaluate a commit.
  • Evaluate a merged commit: Govlin prepares its evidence and computes whether it can ship. Evaluating records nothing.
  • Record a decision (Approved, Risk accepted or Rejected) with its risk level. The approver is the signed-in person and the decision cites the evidence hash.
  • Advanced tools that advise and never approve or block: change risk, CAB packets, the history of CI authorizations and a multi-repository view.

Who: Administrators today.

Computed state, per environment
  • Ready to proceedEverything passes, or only record-only rules fail.
  • With warningsA rule that warns fails.
  • Requires approvalA rule that requires approval fails; Govlin says which and who can approve.
  • BlockedA blocking rule fails; Govlin names the rule.
Human decisions
ApprovedRisk acceptedRejected

Shown apart, with author, date and evidence, and they never change the computed state. Approval, exception and bypass are different things: no decision overrides an absolute block.

04Evidence

What happened and how do I prove it?

Every recent change with its tickets, pipeline, quality and approvals, and the files you hand to an auditor.

  • Changes: commits sent from the Desktop and merged pull requests, searchable by ticket, commit, branch or author, with or without a ticket.
  • The details of a change: origin, author, branch, pipeline, quality result, the real number of pull request approvals, its Jira tickets and files.
  • Download the evidence of a ticket in one step: commits, pull requests, pipeline runs and quality results in one file, which says what is missing.
  • Tickets without code: the Jira tickets no change cites. Audit: export the event history for a date range, see previous exports and review evidence against control frameworks your organization imports.

Who: Everyone sees the changes; tickets without code and Audit need an administrator.

05Rules

What is required and with what effect?

The rules of the repository Govlin detected, in five groups, each with one effect. Govlin never asks which repository.

  • Branches, Commits, Pull requests, Traceability and Quality: protected branches, allowed names, force push, conventional or signed commits, maximum and forbidden files, required reviews, a ticket per change and a green quality gate.
  • One effect per group: Not checked, Warn (the push goes through with a warning) or Block (the push is refused).
  • One level for the whole repository: Observe only, Moderate or Strict. A level changes the effects, never the rules.
  • Where the rules come from (Govlin, a gitgov.toml file in the repository or both, and whether they agree), plus the change history: who, when and which version.

Who: Everyone reads the rules of their repository; only an administrator changes them.

Rules of a repositoryCustom
  • Branches
    Protected branches · allowed names · no force push
    Block
  • Commits
    Conventional · signed · max files · forbidden files
    Warn
  • Pull requests
    Pull request required · minimum approvals
    Warn
  • Traceability
    Every change cites a ticket
    Block
  • Quality
    The quality gate is green
    Not checked
Observe only
Every group off; Govlin still gathers evidence.
Moderate
Every group warns.
Strict
Every group blocks.

Example. When groups have different effects, the level reads as Custom.

06Settings

How is Govlin connected?

Setup, people and access, your account, your preferences and the connection, each in its own section.

  • Setup, six steps: organization profile, integrations, GitHub Actions workflows, workflows in the repository, variables and secrets (names only) and the release approval policy.
  • Organization: people and roles, invitations by GitHub login or email, team activity over 7, 30 or 90 days and access keys for services and CI, shown once.
  • Account: your GitHub identity, your role, a local PIN and sign-out. Preferences: language (English or Spanish), time zone and desktop notifications.
  • System: the server connection, pending deliveries and signed updates on the Stable or Beta channel.

Who: Setup and Organization are for administrators; Account, Preferences and System for everyone.

On every screen

Ask

A conversation on every screen (Ctrl+J). It takes its subject from the screen and never asks for the organization, repository, branch or time window.

  • Ask about the selected change, ticket or release, or about the team's activity: who pushed where and when.
  • Answers come from what Govlin records and cite their sources, with links to where they live in Govlin.
  • Honest by design: when the AI answer is not available, the answer says it is an evidence summary; when data is missing, it says so.

Who: Administrators, architects and PMs. Ask only uses what you could see yourself.

Integrations

What Govlin receives

Each integration once: what it sends to Govlin.

GitHub

Signed webhooks for pushes, branches, pull requests, reviews, review and PR comments, check runs and statuses. Every delivery leaves a receipt, and missing ones are redelivered.

Jira

Tickets through a signed Jira webhook. A change is linked to the tickets its commit message, branch, pull request title or comments cite, when it arrives.

Jenkins

Pipeline runs with job, result, duration and stages, correlated with the commit that triggered them.

SonarQube

Quality gate results linked to the pipeline run and commit they belong to.

GitHub Actions

A reviewed workflow pack generated from your organization profile, installed through a pull request. Govlin checks the variable and secret names, never their values.

Connected · No data · Not set up

This is how Govlin names the state of each integration. Render and Vercel can also be selected in the organization profile.

Try it on your repository

Download Govlin Desktop, sign in with GitHub and open the Action Center.

Download DesktopRead Documentation