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

Using composite action #46

Merged
merged 2 commits into from
Jun 15, 2024
Merged

Using composite action #46

merged 2 commits into from
Jun 15, 2024

Conversation

arash77
Copy link
Collaborator

@arash77 arash77 commented Jun 14, 2024

This pull request introduces the use of a composite action to streamline the workflow. The composite action is responsible for running the necessary steps to preview and publish content.
This is a replacement for #39

@arash77
Copy link
Collaborator Author

arash77 commented Jun 14, 2024

Although it helps organize workflows better, it also requires specifying the tokens multiple times in the files.
That is because it is not possible to use secrets in composite actions.

@arash77
Copy link
Collaborator Author

arash77 commented Jun 14, 2024

Maybe, It is better to save the secrets into env variables in the workflows.
Or, using Reusable Workflow to pass the secrets to env variables.

@arash77 arash77 marked this pull request as draft June 14, 2024 11:30
@arash77 arash77 marked this pull request as ready for review June 14, 2024 14:32
@wm75 wm75 merged commit 6fb5c4a into main Jun 15, 2024
1 check passed
@arash77 arash77 deleted the arash-composite-action branch June 17, 2024 08:14
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.

3 participants