Get GHA pipelines established#141
Draft
TTTriplicate wants to merge 11 commits intoCodeCrow:productionfrom
Draft
Conversation
…ic linux requirement. Getting GHA basic setup established. Commiting lockfiles to maintain dependency version continuity across multiple devs and deployment
…. Also no need for a custom action; should all be manageable in a workflow
TTTriplicate
commented
Dec 19, 2024
| # Get exact command from Rob | ||
| # Feed it the secrets e.g. SECRET__PAYPAL_CLIENT_ID | ||
| # - name: deploy | ||
| # run: fab deploy --environment ${{ inputs.environment }} |
Author
There was a problem hiding this comment.
If you can drop the command here, I can work out the rest
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is still a draft, getting a few last things settled.
Basic idea is this:
productionbranchproductionbranch, e.g. no push to it without approval from @CodeCrowThis will hide the currently exposed secrets from anyone scraping GitHub for exactly that kind of data, as well as automatically maintaining the current Prod version of the website in sync with the current state of code.
TODO
heredocdropping them into a.envrcon the runner, and putting the existing.envrcin the.gitignore