Skip to content

Conversation

@Guilospanck
Copy link
Contributor

Most of the times when contributing code to the repo I find myself only realising that I missed some linting, formatting or checking after the Github Actions job is triggered and fails.

This adds a new just recipe called pre-contributing that aims to help contributors to run a single command before opening a PR, making sure that everything is working correctly and nothing is missing.

@Davidson-Souza
Copy link
Member

ACK 8d9f124

@Davidson-Souza Davidson-Souza merged commit 59978d7 into vinteumorg:master Dec 26, 2024
6 checks passed
Copy link
Contributor

@JoseSK999 JoseSK999 left a comment

Choose a reason for hiding this comment

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

Seems a good idea, I would request a small change

./contrib/clean_data.sh

# Run all needed checks before contributing code
pre-contributing: lint fmt test build-release
Copy link
Contributor

Choose a reason for hiding this comment

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

I would do this instead, as the lint recipe includes formatting, and test-features is the full check run in GitHub Actions.

Suggested change
pre-contributing: lint fmt test build-release
pc: lint test-features

@JoseSK999
Copy link
Contributor

Omg late review 😂😂

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