You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Summary
- some sub-commands of detecting the original branch will not work in a
fork. Piping all to true
## Proof of Work
-
https://spruce.mongodb.com/task/ops_manager_kubernetes_run_pre_commit_run_precommit_and_push_patch_bcd12dc59be1fb83328262689e2b199cc2b08ceb_67ceb328658a1e000760d748_25_03_10_09_38_52/logs?execution=0
```
[2025/03/10 10:39:47.037] Fork: Could not determine the original branch. Running in a fork
```
## Checklist
- [ ] Have you linked a jira ticket and/or is the ticket in the title?
- [ ] Have you checked whether your jira ticket required DOCSP changes?
- [ ] Have you checked for release_note changes?
## Reminder (Please remove this when merging)
- Please try to Approve or Reject Changes the PR, keep PRs in review as
short as possible
- Our Short Guide for PRs:
[Link](https://docs.google.com/document/d/1T93KUtdvONq43vfTfUt8l92uo4e4SEEvFbIEKOxGr44/edit?tab=t.0)
- Remember the following Communication Standards - use comment prefixes
for clarity:
* **blocking**: Must be addressed before approval.
* **follow-up**: Can be addressed in a later PR or ticket.
* **q**: Clarifying question.
* **nit**: Non-blocking suggestions.
* **note**: Side-note, non-actionable. Example: Praise
* --> no prefix is considered a question
0 commit comments