-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project git branch reporting as '(no' when a rebase is in progress #22604
Comments
@kaiyoma thank you for the report. Those area's of the app are intended to display the current git branch for your project, if your project uses git. So either:
Can you confirm:
|
@tbiethman Yes, we're using git, and the branch is named |
@kaiyoma gotcha, I'd expect that to work just fine. Let's see what the logs tell us. Could you try running Cypress with the DEBUG env set like below?
That should output the detected git settings for your project. If you see '(no' in the logs, then we have a detection problem. If you see 'trunk', then we have a processing problem. |
|
Thanks @kaiyoma , that appears to be a parsing issue from simple-git, the dependency we use within Cypress to retrieve your project's git info. My guess here is that it's parsing some sort of error message that git outputs when we call the I wrote a small isolation script that you could run from your project root. I'm curious what the output may be for you? It's likely still going to show |
@tbiethman Here you go: Click to expand full console output
|
@tbiethman Ah, I think I figured it out: this problem happens only when editing a commit during a |
@kaiyoma Nice find! I can reproduce the same by loading cypress during a rebase. The branch gets reported as something like: Which then turns into We'll have to see if there are mitigating steps we can take or work with simple-git to get better output here. |
((no)
mean?
This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided. |
AFAIK this is still an issue. |
This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided. |
This issue has been closed due to inactivity. |
Current behavior
In several places in the Cypress UI, I'm seeing the text
((no)
. What does this mean?Desired behavior
No response
Test code to reproduce
Run Cypress.
Cypress Version
10.3.0
Other
No response
The text was updated successfully, but these errors were encountered: