Skip to content

Making the python check in codecheck truly optional#1390

Merged
carlocamilloni merged 1 commit intoplumed:masterfrom
Iximiel:fix/codecheck-python-requisites
Apr 3, 2026
Merged

Making the python check in codecheck truly optional#1390
carlocamilloni merged 1 commit intoplumed:masterfrom
Iximiel:fix/codecheck-python-requisites

Conversation

@Iximiel
Copy link
Copy Markdown
Member

@Iximiel Iximiel commented Apr 1, 2026

Description

I thought the new checks I added to codecheck to be optional. With the new guards now are truly optional, and I moved the cython code check to be "global" only, that has more sense.

Target release

I would like my code to appear in release V2.11

Type of contribution
  • changes to code or doc authored by PLUMED developers, or additions of code in the core or within the default modules
  • changes to a module not authored by you
  • new module contribution or edit of a module authored by you
Copyright
  • I agree to transfer the copyright of the code I have written to the PLUMED developers or to the author of the code I am modifying.
  • the module I added or modified contains a COPYRIGHT file with the correct license information. Code should be released under an open source license. I also used the command cd src && ./header.sh mymodulename in order to make sure the headers of the module are correct.
Tests
  • I added a new regtest or modified an existing regtest to validate my changes.
  • I verified that all regtests are passed successfully on GitHub Actions.

@Iximiel Iximiel changed the title adding more guards for the local run of codecheck Making the python check in codecheck truly optional Apr 1, 2026
@carlocamilloni carlocamilloni merged commit 53abff6 into plumed:master Apr 3, 2026
45 of 52 checks passed
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.

2 participants