Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore(ci): Add CRLF detection and fix targets to prevent CRLF contamination#1898

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
kakkoyun wants to merge1 commit intoprometheus:main
base:main
Choose a base branch
Loading
fromkakkoyun:feature/crlf-detection

Conversation

@kakkoyun
Copy link
Member

Add two new Makefile targets to detect and fix carriage return (CRLF)
line endings that can contaminate the codebase from Windows environments:

  • check-crlf: Scans all text files (excluding hidden dirs and vendor)
    for CRLF line endings and fails if any are found
  • fix-crlf: Automatically converts CRLF to LF using the tr command

Add CRLF check to CI workflow to catch line ending issues early in PRs.
The check runs immediately after checkout, before any other validation.

Also rename go.yml to validate.yml to better reflect the workflow's
purpose, and fix job name casing (supportedVersions -> supported_versions).

Signed-off-by: Kemal Akkoyunkemal.akkoyun@datadoghq.com

…nationAdd two new Makefile targets to detect and fix carriage return (CRLF)line endings that can contaminate the codebase from Windows environments:- check-crlf: Scans all text files (excluding hidden dirs and vendor)  for CRLF line endings and fails if any are found- fix-crlf: Automatically converts CRLF to LF using the tr commandAdd CRLF check to CI workflow to catch line ending issues early in PRs.The check runs immediately after checkout, before any other validation.Also rename go.yml to validate.yml to better reflect the workflow'spurpose, and fix job name casing (supportedVersions -> supported_versions).Signed-off-by: Kemal Akkoyun <kemal.akkoyun@datadoghq.com>
Copy link
Member

@bwplotkabwplotka left a comment

Choose a reason for hiding this comment

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

Thanks! One nit only

steps:
-name:Checkout code
---
name:Validate
Copy link
Member

Choose a reason for hiding this comment

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

Can we keep Go name (also in file)? Otherwise we need to change GH CI required checks and generally change the experience of contributing to client_golang. Is it worth the name change?

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@bwplotkabwplotkabwplotka approved these changes

@ArthurSensArthurSensAwaiting requested review from ArthurSensArthurSens is a code owner

@vesarivesariAwaiting requested review from vesarivesari is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@kakkoyun@bwplotka

[8]ページ先頭

©2009-2025 Movatter.jp