Skip to content
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

Fix: Explicitly pass secrets to reusable workflows #1837

Merged
merged 1 commit into from
Dec 17, 2024

Conversation

niyajali
Copy link
Collaborator

This commit explicitly passes secrets to reusable workflows, rather than relying on inheritance. This addresses an issue with reusable workflows not inheriting secrets as expected.

  • The secrets: inherit statement has been removed from the multi-platform-build-and-publish and promote-to-production workflows.
  • Instead, secrets are explicitly defined in the secrets section of each workflow, ensuring that the reusable workflows have access to the necessary secrets.

Issue Fix

Fixes #{Issue Number}
Jira Task: Task_Number

Screenshots

Description

  • Apply the AndroidStyle.xml style template to your code in Android Studio.

  • Run the unit tests with ./gradlew check to make sure you didn't break anything

  • If you have multiple commits please combine them into one commit by squashing them.

This commit explicitly passes secrets to reusable workflows, rather than relying on inheritance. This addresses an issue with reusable workflows not inheriting secrets as expected.
- The `secrets: inherit` statement has been removed from the `multi-platform-build-and-publish` and `promote-to-production` workflows.
- Instead, secrets are explicitly defined in the `secrets` section of each workflow, ensuring that the reusable workflows have access to the necessary secrets.
@therajanmaurya therajanmaurya merged commit b5c0b36 into openMF:dev Dec 17, 2024
7 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