Our Mac menu plugin now includes upcoming Scheduler events and custom date display formats.
Update the plugin to unlock this new config:
Then view upcoming freezes and unfreezes directly from your Mac's menu bar:
Branch API endpoints now include new attributes
next_unfreeze_at epoch timestamps.
GitHub Invoiced customers may now manage subscriptions self-service. Learn more.
Enable Slack notifications for scheduled freezes to stay in the loop on Merge Freeze automations.
Fetch freeze logs for an entire installation or single repository via the API, for internal analysis or otherwise. Learn more.
Mac users - manage projects directly from your computer's menu bar. Learn more.
Schedule upcoming freezes (+ accompanying unfreezes) via the API. Learn more.
curl -d "access_token=xxx&account=merge-freeze&repository=core&branch=master\ &one_off_freeze_at=1669740656&one_off_unfreeze_at=1669999856" \ -X POST https://www.mergefreeze.com/api/scheduled_freezes
Batch unfreeze a selection of projects from your dashboard in 1 click.
Our status page got a huge makeover. Subscribe to alerts, review incidents, and inspect service health on a granular basis.
UX improvement - unfreeze single PRs by their name vs GitHub integer ID.
Freeze a custom selection of projects in 1 click.
Formerly executed "one-off" freezes are now visible in the Scheduler interface for future reference, e.g. comparison with internal logs.
Need to rotate API credentials with zero downtime? Now you can. Create org-wide tokens from your installation's settings page, then regenerate branch-level tokens as needed.
You asked, we listened! You may now "freeze with note" via the API (
note=XXX param) or Slack integrations. Note: GitHub only shows the first ~50 characters. Learn more.
The "Details" link inside your GitHub > Pull Request interfaces now goes directly to the branch's dashboard inside Merge Freeze, versus the homepage.
Create new branches (projects) directly from the API. Set a default "frozen" status, generate an access token, and set admin access in 1 request. Learn more.
Restrict permissions for Slack
/mergefreeze commands to only developers on your team using Merge Freeze. Learn more.
You may now freeze or unfreeze a single PR (while maintaining the overall freeze) via the Web API.
curl -d "frozen=true&user_name=Scooby Doo&unblocked_prs=" -X POST https://www.mergefreeze.com/api/branches/mergefreeze/core/master/?access_token=[Your access token]
/mergefreeze command now handles an unlimited number of repositories integrated with your account.
Basic audit logs are now available. View a live feed of installation activity on your dashboard.
We have a status page! Check it out at https://mergefreeze.com/status.
Login cookies no longer cause the web UI "freeze" feature to fail after idling on the browser tab.
We've added a more flexible system for creating scheduled freezes. Previously the only option was to create weekly recurring freezes. You can now have much more customized scheduled freezes for example "Every 2 weeks on a Friday" or "Every 3rd Monday of the month".
One-off scheduled freezes are now also possible.
We've added a bunch more options to our Slack integration. You can now unblock / re-block single pull requests through Slack and unblock / re-block deployments. Notifications for these actions are also sent to Slack now.
You can now unblock multiple pull requests when a freeze has been implemented. Previously you could only unblock one, and if you needed to unblock another one you'd have to re-block the first one, which was super annoying. But no longer!
It's now possible to freeze or unfreeze your project via the web API.
To freeze or unfreeze you'll need to send a POST request. Here's an "freeze" request example:
curl -d "frozen=true&user_name=Scooby Doo" -X POST https://www.mergefreeze.com/api/branches/my-org-name/my-repo-name/master/?access_token=[my-access-token]
We have a new logo! Not sure what to name him yet. Freezy McFreezeface?
We have now implemented non-admin restrictions on many actions that were previously able to be performed by anyone who had access to a repository.
From now on, only repository administrators may:
We've just released a new way of implementing a merge freeze, so now you have two options.
Option 1: Push a status update to all PRs (default)
Option 2: Toggle a branch protection rule