You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These variables are defined with := rather than ?= which means it's not possible to override these variables, they will always be overwritten by the values set in the build-harness module Makfile. We use GitLab and need to override these variables to be able to load the template from GitLab and to be able to allowlist our organisation. Without these changes, it is not possible for us to use the README module without forking build-harness to add our changes.
Expected Behavior
The variables do not override values set previously.
Steps to Reproduce
Add to the Makefile before including the build-harness bootstrap:
It still works to set README_TEMPLATE_FILE and this will prevent attempts to fetch the remote template. If you have issues with dirname outputting errors it may be because no github_repo line is present in your README.yaml, for example because you use GitLab instead. In this case, setting README_TEMPLATE_REPO_ORG will mean that it doesn't attempt to discover that from the README.yaml. You can set it to any value for as long as README_TEMPLATE_FILE exists, it will be ignored.
Describe the Bug
These variables are defined with
:=
rather than?=
which means it's not possible to override these variables, they will always be overwritten by the values set in the build-harness module Makfile. We use GitLab and need to override these variables to be able to load the template from GitLab and to be able to allowlist our organisation. Without these changes, it is not possible for us to use the README module without forking build-harness to add our changes.Expected Behavior
The variables do not override values set previously.
Steps to Reproduce
Add to the Makefile before including the build-harness bootstrap:
Notice how using the README module, this is overwritten to the original GitHub version.
Screenshots
No response
Environment
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: