# Why is my commit not visible in Swarmia?

## If the commit belongs to a pull request

Check that the pull request is visible in Swarmia:

* [The repository](https://app.swarmia.com/settings/repositories) is synced to Swarmia
* The pull request is not [excluded](https://app.swarmia.com/settings/pull-requests)
* The pull request is assigned to the [correct team](https://app.swarmia.com/settings/team/pull-requests)

## If the commit doesn't belong to a pull request

We include only commits from pull requests.

The primary reason for this behavior is to avoid cluttering the [work log](https://help.swarmia.com/use-cases/improve-your-teams-focus/analyzing-the-activity-patterns-on-work-log) with commits that may not represent "real work". Workflows involving rebasing can create numerous duplicate or temporary commits, and including them would make the worklog noisy and could misrepresent development activity. Swarmia's model assumes that development work is captured through pull requests.

As a result, daily commits made to a feature branch will remain invisible in Swarmia until a PR is created.

The only exception is the "[avoid pushing directly to the default branch](https://app.swarmia.com/working-agreements/explore/no-direct-pushes-to-main-branch)" working agreement, which follows commits pushed directly to the default branch of each repository.

{% hint style="info" %}
Tip: If you'd like to get faster visibility into commits, you can create draft pull requests for your work in progress.
{% endhint %}