-
Notifications
You must be signed in to change notification settings - Fork 123
[FLOSS H1] build server check: only allow a-z, 0-9 and _ for file names #1615
Comments
Latest results:
Ideally we would have a script that automatically renames everything based on conventions, in the same way we have it with clang-format. I'd prefer not to have to discuss about such conventions 😉 At the moment |
The guideline now is |
I mark this issue stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping the issue by writing a message here or create a new issue with the remainder of this issue. |
[FLOSS H1] When I run
As far as I can tell these violations are only in the build directory, so I can confirm the guideline is not violated by the project. |
@muskater it is easier to do such verification in a clean clone. I also tried the command, and |
CLion requires the template name to be Having a template for header files is definitely a nice addition. I agree, the best solution would be to have a separate allow list for these kind of corner cases. |
…onform to the file naming convention as discussed in ElektraInitiative#1615. This script is executed at the cirrus CI and the Jenkins CI.
…onform to the file naming convention as discussed in ElektraInitiative#1615. This script is executed at the cirrus CI and the Jenkins CI.
We have inconsistent use of characters in file names, which always requires one to think which kind of separator is used in specific cases.
As short time goal we should not introduce new variants (such as spaces, see #1613), as 1.0 goal I propose to unify it to a single variant.
The text was updated successfully, but these errors were encountered: