Skip to content

Move configuration env mapping to top of workflow #164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 2, 2025

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented Jun 2, 2025

The "Release" GitHub Actions workflow is based on a standardized "template" which is designed to be reusable in any relevant project.

Some project-specific configuration of the the workflow must be done. These are done via workflow environment variables. It will be most convenient to place the env mapping were these variables are defined at the top of the workflow to make them easily accessible to the project maintainer.

The "Release" GitHub Actions workflow is based on a standardized "template" which is designed to be reusable in any
relevant project.

Some project-specific configuration of the the workflow must be done. These are done via workflow environment variables.
It will be most convenient to place the `env` mapping were these variables are defined at the top of the workflow to
make them easily accessible to the project maintainer.
@per1234 per1234 self-assigned this Jun 2, 2025
@per1234 per1234 added type: enhancement Proposed improvement topic: infrastructure Related to project infrastructure labels Jun 2, 2025
@per1234 per1234 merged commit 72b6f2d into arduino:master Jun 2, 2025
11 checks passed
@per1234 per1234 deleted the move-env branch June 2, 2025 06:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: infrastructure Related to project infrastructure type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant