Add push to another repository workflow #7
Conversation
This file contains 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
|
I need to check the typos :D |
|
|
||
| ## The problem | ||
| Sometimes we need push code from `Repository A` | ||
| action to `Repository B` codebase, for eg. when we are implementing |
There was a problem hiding this comment.
Suggested change
| action to `Repository B` codebase, for eg. when we are implementing | |
| action to the `Repository B` codebase, for e.g., when we are implementing |
There was a problem hiding this comment.
it should be e.g. or for example, "for" is already included in e.g. :D
| ## The problem | ||
| Sometimes we need push code from `Repository A` | ||
| action to `Repository B` codebase, for eg. when we are implementing | ||
| GitOps(for the deployment repo) or when we need separate repo for build |
There was a problem hiding this comment.
Suggested change
| GitOps(for the deployment repo) or when we need separate repo for build | |
| GitOps(for the deployment repo) or when we need separate repo for the build |
| Sometimes we need push code from `Repository A` | ||
| action to `Repository B` codebase, for eg. when we are implementing | ||
| GitOps(for the deployment repo) or when we need separate repo for build | ||
| process for eg. with Design Tokens. |
There was a problem hiding this comment.
Suggested change
| process for eg. with Design Tokens. | |
| process for e.g. with Design Tokens. |
| 4) Go to source repo(`Repository A`). | ||
| 5) Go to `Settings` > `Secrets` > `Actions`. | ||
| 6) Click `New repository secret`. | ||
| 7) Add name for eg. `DEPLOY_SSH_KEY` - remember it must match variable name used in workflow. |
There was a problem hiding this comment.
Suggested change
| 7) Add name for eg. `DEPLOY_SSH_KEY` - remember it must match variable name used in workflow. | |
| 7) Add a name for e.g. `DEPLOY_SSH_KEY` - remember it must match the variable name used in the workflow. |
qbart
reviewed
Nov 7, 2022
| # Push to another repository | ||
|
|
||
| ## The problem | ||
| Sometimes we need push code from `Repository A` |
There was a problem hiding this comment.
Suggested change
| Sometimes we need push code from `Repository A` | |
| Sometimes we need to push the code from `Repository A` |
qbart
reviewed
Nov 7, 2022
| process for eg. with Design Tokens. | ||
|
|
||
| ## Solution | ||
| We can leverage GitHub deploy keys(https://docs.github.com/en/developers/overview/managing-deploy-keys), heres how: |
There was a problem hiding this comment.
Suggested change
| We can leverage GitHub deploy keys(https://docs.github.com/en/developers/overview/managing-deploy-keys), heres how: | |
| We can leverage GitHub deploy keys ([managing deploy keys](https://docs.github.com/en/developers/overview/managing-deploy-keys)), here is how: |
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.
No description provided.