🛠️ 📚💡 This is a detailed and carefully made template for your GitHub projects. It's based on the wide knowledge and practical experience of the engineering community within NHS England. The template includes helpful suggestions, standards and practices - it's something you should consider using for all your repositories.
MIT License
30
stars
12
forks
source link
Decide what to do with the `Docker image versions` section in the `.tool-versions` file #134
Currently, the recommendation is to use the .tool-versions file to store versions of the toolchain dependencies, which include dependencies specific to the built-in functionality of the repository template. This comes with the problem of unclear ownership of this file.
See PR #133
What is the feature that you are proposing to solve the problem?
Move the dependency versions for the repository template out of the .tool-versions file.
What alternatives have you considered?
The options are:
Keep them where they are and use the update-from-template-app automated process to introduce and reconcile changes.
Create a separate versions file for the dependencies of the repository template.
Store the versions inline in the scripts where they are required.
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Sensitive Information Declaration
[X] I confirm that neither PII/PID nor sensitive data are included in this form
What is the problem this feature will solve?
Currently, the recommendation is to use the
.tool-versionsfile to store versions of the toolchain dependencies, which include dependencies specific to the built-in functionality of the repository template. This comes with the problem of unclear ownership of this file.What is the feature that you are proposing to solve the problem?
Move the dependency versions for the repository template out of the
.tool-versionsfile.What alternatives have you considered?
The options are:
Code of Conduct
Sensitive Information Declaration