GitHub & GitLab Commit Alerts
Follow the commits on a branch, the commits that touch one file or folder, a file's own text, or a GitLab project's issues and merge requests. Enter a repository, choose what to follow, and see the exact address PageCrawl will monitor, with its latest entries, before you continue.
GitHub & GitLab Commit Alerts
Follow commits to a branch, folder or file, a file's text, or GitLab issues and merge requests.
Type owner/repo, or paste any github.com or gitlab.com address: a repository, a branch, a folder, a file or a feed.
On a self-managed server the form follows the project's Releases page with Full Page Text. If your server publishes a feed address, paste it in the field above instead.
Try an example:
Blank follows the default branch. Slashes work, such as release/1.95.
A file such as LICENSE.txt, or a folder such as doc/api.
Only commits by this person.
Only items with every label you list.
Address we'll monitor
Open the address in a new tabEnter a repository to see the address we will monitor.
The AI uses this when it summarizes each new item and rates how important it is. Edit it to fit what you care about.
Notify me
Each change: an alert after the check that finds it. A digest batches alerts into one email, which you switch on after setup.
Read the full guide
This form sets up the monitor. The guide covers which pages to monitor, the setup step by step, and how to get fewer, better alerts.
How to Track Commits to a GitHub or GitLab Repository, Branch or File Track commits to a GitHub or GitLab branch, folder or single file through the Atom feeds both sites publish, and get alerted when a license or changelog changes. Read the guideHow it works
- Enter a repository, or paste any address from it: a branch, a folder, a file or a feed.
- Choose what to follow. The branch and path are filled in from what you pasted, and you can change them.
- See the address PageCrawl will monitor, how it is tracked, and its latest entries.
- Continue to PageCrawl, review the setup and start tracking. The first check records what is there now, so existing entries never alert you.
Frequently asked questions
How do I get alerts for commits to one file on GitHub?
Use the file's commit feed, https://github.com/{owner}/{repo}/commits/{branch}/{path}.atom, for example https://github.com/redis/redis/commits/unstable/LICENSE.txt.atom. Each commit that touches the file becomes a new item on the next check, with the commit message and a link. Enter the repository, branch and path above, and the form shows the exact address before you continue.
What are the GitLab addresses for commits, tags and merge requests?
On gitlab.com, commits are at /-/commits/{branch}?format=atom, with a file or folder path after the branch, tags at /-/tags?format=atom (the look-alike /-/tags.atom redirects to the sign-in page) and releases at /-/releases.atom. Issues and merge requests are at /-/issues.atom and /-/merge_requests.atom, and both keep list filters such as ?state=merged or label_name[]=bug. Project paths can include nested groups, and group-wide lists live at https://gitlab.com/groups/{group}/-/issues.atom.
Should I watch the commit feed or the file itself?
Watch the commit feed to learn that a file changed and why, in the author's own words. Watch the raw file, https://raw.githubusercontent.com/{owner}/{repo}/{branch}/{path} or /-/raw/{branch}/{path} on GitLab, with Full Page Text and Everything selected to see exactly which lines changed. For a license or a changelog, run both. Very large files are capped, and only the beginning is kept.
Will a busy branch flood me with alerts?
Narrow the address first: a file or folder path instead of the whole branch, ?author={username} on GitHub, or ?state=merged on a GitLab merge request feed. A busy feed can also go into a daily or weekly digest. The first check is a silent baseline, so the commits already in the feed never trigger an alert.
Can I follow GitHub issues or pull requests?
Not through a feed. GitHub publishes none for issues, pull requests or security advisories, and issues.atom answers with an HTTP 406 error. Use the repository's Watch menu instead: choose Custom, then Issues or Pull requests. GitLab does publish issue and merge request feeds, and the form above sets them up with your state and label filters.
Does it work with self-managed GitLab?
Yes. Self-managed servers publish the same addresses under their own domain. Some only answer visitors using a regular browser, so if a feed cannot be read, monitor the project's Releases page with Full Page Text instead, which is what the form's Self-managed option sets up. Paste a feed address from your server to monitor it as it is.
Monitor any web page for changes
PageCrawl watches any page and alerts you when a check finds something important changed. Set up your first monitor in under a minute.
Start free