Explore

Explore shows what is happening on the forge for the open repository: its pull requests, issues, and workflow runs. Open it with the Explore tab beside History and Review.

Explore needs a forge connection for the repository's forge, and the repository has to be approved on this device. Until then, Explore shows Repository approval required with a button to fix it.

The Explore sidebar has three sections:

• Pull requests, where Explore opens;
• Issues;
• Actions, for workflow runs and pipelines.

Selecting an item opens it in the main area, with its details in the Details panel. Back and forward move through what you have opened. Search forge in the command palette, or Cmd+F / Ctrl+F in Explore, moves to the search field.

Pull requests

The list can be narrowed from All authors to Opened by me, Review requested, or Drafts. A pull request shows its conversation, reviews, commits, files, and checks.

From a pull request you can:

• comment, and approve or request changes;
• merge it on the forge, which still applies the forge's required checks and branch rules;
• Mark ready or Convert to draft, Close pull request or Reopen, and edit its title, description, Labels…, Assignees…, and reviewers;
• Check out… the pull request at its current revision; commit or stash local changes first;
• open it in Review to review it file by file;
• Open on forge in your browser.

Create pull request compares two branches in your clone before you create it. The file list and diffs of a pull request come from your local clone when it has the commits, so large pull requests load quickly.

Issues

The Issues section lists the repository's issues. Open one to read and add comments, edit it, change its labels and assignees, or close and reopen it. Create issue opens a new one.

Actions

Actions lists Recent runs and Workflows. Open a run to see its jobs, their logs, and its artifacts. While a run is still going, Explore follows it and refreshes it until it finishes.

Depending on the forge, you can Re-run a run, Re-run failed jobs, Re-run job, Cancel run, and Approve workflow for a run that waits for approval.

Start a workflow run

1. In Workflows, select a workflow and choose Run workflow….
2. Choose the branch or tag to run on and fill in the workflow's inputs. The form reads the inputs from the workflow file on the forge at that ref, because that is the file the forge will run.
3. Confirm. GitComet Pro asks before every run, because a run cannot be undone, and never retries one on its own.

Explore then selects the new run and follows it. Starting runs works on GitHub, GitLab, Gitea and Forgejo, Bitbucket Cloud, and Azure DevOps. Bitbucket Data Center has no pipelines to start.

Configuration that a workflow file includes or imports from elsewhere is not read, and the form says so.

What Explore can do depends on your token

Explore can never do more than your forge account and its credential allow. If an action fails or is missing, check the permissions listed for your forge in Forge Connections.