-
Notifications
You must be signed in to change notification settings - Fork 209
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
adding details to change github action to point to serverless endpoint #204
Merged
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
mettin
approved these changes
Oct 10, 2023
kirillsud
reviewed
Oct 10, 2023
Comment on lines
+209
to
+212
8. Lastly, you will need to change the URL in the GitHub action to point to your own deployed serverless functions. Point your GitHub action for `issues` to point to your `issues` endpoint from your serverless functions. The same should be done for `project-cards`. | ||
Go to [.github/workflows/issues.yml](.github/workflows/issues.yml) and change the URL on [line 11](.github/workflows/issues.yml#L11). | ||
Go to [.github/workflows/project-cards.yml](.github/workflows/project-cards.yml) and change the URL [on line 13](.github/workflows/project-cards.yml#L13). | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks a bit ugly. Are these "go to" supposed to be as list items?
Suggested change
8. Lastly, you will need to change the URL in the GitHub action to point to your own deployed serverless functions. Point your GitHub action for `issues` to point to your `issues` endpoint from your serverless functions. The same should be done for `project-cards`. | |
Go to [.github/workflows/issues.yml](.github/workflows/issues.yml) and change the URL on [line 11](.github/workflows/issues.yml#L11). | |
Go to [.github/workflows/project-cards.yml](.github/workflows/project-cards.yml) and change the URL [on line 13](.github/workflows/project-cards.yml#L13). | |
8. Lastly, you will need to change the URL in the GitHub action to point to your own deployed serverless functions. Point your GitHub action for `issues` to point to your `issues` endpoint from your serverless functions. The same should be done for `project-cards`. | |
- Go to [.github/workflows/issues.yml](.github/workflows/issues.yml) and change the URL on [line 11](.github/workflows/issues.yml#L11). | |
- Go to [.github/workflows/project-cards.yml](.github/workflows/project-cards.yml) and change the URL [on line 13](.github/workflows/project-cards.yml#L13). |
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.