Bitrise: Inconsistent merge refs in Git Clone Repository Step
Timeline of updates
- resolved
We saw some issues in our Git Clone Repository Step when checking out the merge ref for a Pull Request: sometimes the merge ref was referencing an old commit which is incorrect. v7 version of this step introduced relying on merge refs, we rolled back to manual merging (6.2.2 version of the step) until further investigation. The fixed version is published as 7.0.3 so everyone using the latest pinned major 7.x.x (or minor 7.0.x) version will get the update automatically.
From Bitrise’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.bitrise.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Bitrise, started 2023-02-06 20:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Inconsistent merge refs in Git Clone Repository Step
- Vendor
- Bitrise
- Date
- URL
- https://rewindex.com/company/bitrise/incidents/j67ndj7d7l39
Bitrise profileRecent Bitrise incidentsAll outages on February 6, 2023Bitrise in February 2023MarkdownJSON