Skip to content
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

Add a section in the README on how to fix line break encoding issue #396

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

AlexFalessi
Copy link
Member

No description provided.

`The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in ...` can appear for each file having an issue.

To fix the problem the encoding must be consistent in automation-dashboard and all the sub-projects. We will use Dos2Unix tool To achieve that.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To fix this issue, the encoding has to be consistent in automation-dashboard including all its sub-projects

@@ -112,6 +112,26 @@ Then build automation-dashboard, that will compose all subviews.

In order to test subviews and automation dashboard locally, it is required not to publish the subviews archives to main repository, but to local repository of machine.

### Line break issue:
If you are building automation dashboard or subviews using different OS over time you can face an encoding issue. It usually manifest with
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please make sure to mention that it occurs particularly on Windows as it never occurred before on linux or Mac. It will probably never occur on Linux because you cannot merge it if on this repo because Jenkins compilations will fail.

@AlexFalessi
Copy link
Member Author

AlexFalessi commented Sep 1, 2020

Thanks for your comments.
I am checking the use of .gitattributes file to prevent this problem.
Thanks for the tip Fabien.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants