Closed francisfuzz closed 1 week ago
🤔 no idea why CI is not triggered for PRs coming from forks?
🤔 no idea why CI is not triggered for PRs coming from forks?
@gr2m - Great question! From Controlling changes from forks to workflows in public repositories:
Although workflows from forks do not have access to sensitive data such as secrets, they can be an annoyance for maintainers if they are modified for abusive purposes.
To help prevent this, workflows on pull requests to public repositories from some outside contributors will not run automatically, and might need to be approved first. By default, all first-time contributors require approval to run workflows.
and might need to be approved first
Right, I remember the UI for this, I see it on other projects. But didn't see it for the PRs in this repository. I'm probably on some staff flag that turns on an alternative UI that does not have that feature implemented yet
Confirmed, I see it in the classic view:
Good to know, will just switch back-and-forth as needed. Thank you @francisfuzz!!
:tada: This PR is included in version 4.0.2 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Summary
Fixes https://github.com/copilot-extensions/preview-sdk.js/issues/69
This adds a
.gitignore
to the repository, sourced from https://github.com/github/gitignore/blob/main/Node.gitignore 😉