-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
ensure_git_status_clean
documentation confusing wording for ignored
parameter
#19818
Comments
It seems like you have not included the output of |
It looks like you're right, it's not a bool flag, it's a string parameter. fastlane/fastlane/lib/fastlane/actions/ensure_git_status_clean.rb Lines 8 to 15 in e215bdc
|
Actually, even worse is the actual command being run is wrong. It needs to be: git status --porcelain --ignored=#{ignored_file} if you run it without the equals sign it basically always comes back as empty because it is using "no" as the ... for the git-status command. I would consider this a show stopper (critical). The consequence: if you use it with ensure_git_status_clean(
ignored: 'no'
)
begin
...
ensure
reset_git_repo(
disregard_gitignore: false,
)
# Potentially all uncommitted files lost now because ensure_git_status_clean did not raise correctly
end |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
Still an issue |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
Still an issue |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
still an issue |
I'm here too |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
still an issue |
And still an issue. The PR to at least fix the documentation issue is open here: #20976 But imho the underlaying issue still persists. |
I can rename that PR and also fix the issue. Would you be willing to test it? As I'm not currently using that action. |
I could try at least. Never built fastlane from source so far. :) |
You don't have to 😁 I added the testing steps in the PR description |
https://docs.fastlane.tools/actions/ensure_git_status_clean/
For the parameter
ignored
the description says "The flag whether to ignore file the git status if the repo is dirty"I'm not clear on what that means. Looks like a typo.
Thank you
The text was updated successfully, but these errors were encountered: