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

Linter checks go versions in Dockerfile and YAML files #8211

Closed
wants to merge 2 commits into from

Conversation

ffranr
Copy link
Collaborator

@ffranr ffranr commented Nov 20, 2023

Change Description

This PR adds two checks to the linter. These checks ensure that the Go version used in Dockerfile files and YAML files are consistent and as expected.

Steps to Test

Check to ensure that the CI linter Go version check output is correct.

Pull Request Checklist

Testing

  • Your PR passes all CI checks.
  • Tests covering the positive and negative (error paths) are included.
  • Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

📝 Please see our Contribution Guidelines for further guidance.

@ffranr ffranr changed the title Check go versions Linter checks go versions in Dockerfile and YAML files Nov 20, 2023
@guggero guggero self-requested a review November 27, 2023 22:29
@ffranr ffranr self-assigned this Nov 30, 2023
Copy link
Collaborator

@guggero guggero left a comment

Choose a reason for hiding this comment

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

Approach ACK.

Makefile Show resolved Hide resolved
tools/check-go-version-dockerfile.sh Show resolved Hide resolved
local required_go_version="$2"

# Use grep to find lines with 'go:'
local go_lines=$(grep -i '^\s*go:\s*"[0-9]\+\.[0-9]\+\.[0-9]\+"' "$yamlfile" || true) # Ignore grep exit status
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit: move comment to before the line to not make it even longer?

@lightninglabs-deploy
Copy link

@ffranr, remember to re-request review from reviewers when ready

@lightninglabs-deploy
Copy link

Closing due to inactivity

4 similar comments
@lightninglabs-deploy
Copy link

Closing due to inactivity

@lightninglabs-deploy
Copy link

Closing due to inactivity

@lightninglabs-deploy
Copy link

Closing due to inactivity

@lightninglabs-deploy
Copy link

Closing due to inactivity

@ellemouton
Copy link
Collaborator

following the orders of the bot 🤓 feel free to re-open!

@ffranr
Copy link
Collaborator Author

ffranr commented Jul 30, 2024

@guggero Thanks for the review! I've addressed your comments here: #8954
I couldn't reopen this PR, I think because I forced push before re-opening, not sure.

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

Successfully merging this pull request may close these issues.

5 participants