-
Notifications
You must be signed in to change notification settings - Fork 154
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
Fix NOTICE.txt line endings #6911
Conversation
This pull request does not have a backport label. Could you fix it @intxgo? 🙏
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code changes make sense to me and I am surprised how we managed all this time to not run into this with mixed line endings in the NOTICE.txt
thanks for the fix @intxgo . My LGTM will come when CI is green 🙂
|
* dos2unix NOTICE.txt * add dos2unix step to notice generator
* dos2unix NOTICE.txt * add dos2unix step to notice generator (cherry picked from commit 467ece4)
* dos2unix NOTICE.txt * add dos2unix step to notice generator (cherry picked from commit 467ece4) Co-authored-by: Leszek Kubik <[email protected]>
What does this PR do?
The
NOTICE.txt
contains mixed line endings, as produced bymage notice
command. This PR adds equivalent ofdos2unix NOTICE.txt
to the generator to fix this.Why is it important?
mage notice
produces incompatible NOTICE.txt changes on windows, which cannot then be fixed bydos2unix
, etc, because the CI keeps producing file with mixed line endings.Checklist
./changelog/fragments
using the changelog toolDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself