-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Adding forge api calls for project ids #1275
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
Conversation
shotah
commented
Jan 13, 2022
- Adding setup script to take project ids and download them from forge.
- Broke out testing into separate folders so Setup Only can be called separately or together
- Added CI and Discord workflows
…e just setuponly tests, added CI and Discord workflows
|
@itzg The code is passing now in CI. Looks like the PR is still failing due to using Github secrets. |
itzg
left a comment
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.
Great contribution! Just a couple of minor things and this is good to merge.
.github/workflows/discord.yml
Outdated
|
|
||
| on: | ||
| workflow_run: | ||
| workflows: ["ContinuousIntegration", "PullRequest" ] |
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.
...and then can
| workflows: ["ContinuousIntegration", "PullRequest" ] | |
| workflows: ["Build and publish multiarch", "PullRequest" ] |
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.
definitely will add build and publish. Will wait for your comment on CI first to remove ci.
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.
Did you want "Build and Publish" on there as well?
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.
Yes please
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.
Not sure if this is what you are waiting on, but they were already added. Let me know.
workflows: ["ContinuousIntegration", "PullRequest", "Build and Publish", "Build and publish multiarch" ]
Co-authored-by: Geoff Bourne <itzgeoff@gmail.com>
Co-authored-by: Geoff Bourne <itzgeoff@gmail.com>
…cord, using vanilla_version inplace of version
|
Run on lastest changes: |
.github/workflows/discord.yml
Outdated
|
|
||
| on: | ||
| workflow_run: | ||
| workflows: ["ContinuousIntegration", "PullRequest" ] |
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.
Yes please
| timeout-minutes: 5 | ||
| steps: | ||
| - name: notify | ||
| if: github.event.label.name == 'enhancement' || github.event.label.name == 'bug' |
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.
Oh...I think the example I had found was looking at event.issue.labels, but instead it looks like what you have used is exactly what I was wanting in the first place in pr.yml.
itzg
left a comment
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.
Sorry that I really dragged out the review on this one. Great addition!