Test CircleCI

[melissawm]

Testing CircleCI from forks.

[DragaDoncila]

@melissawm since you're looking at this I will note that it doesn't even seem to matter if it's from forks or not 😭 (I can't find a PR right now from this repo but I'm sure there have been some...)

[DragaDoncila]

Ok here's one from not a fork and the preview was still skipped: #84

[melissawm]

I think it may have to do with this: https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#workflows-in-forked-repositories

But still debugging

[melissawm]

I think we can't use the on: pull request trigger. I don't see this example in the action README and due to the link I mentioned above I think that creates permissions issues on forks. We can give this one a try - I think it will only run after merged to main, but you can see already it was not skipped - just wasn't triggered from the last commit.

[melissawm]

See this note in the action readme:

Note: The standard PR-to-main-repo-from-branch-in-a-fork workflow might not activate the action. For changes to take effect, changes might need to be made to to the default branch in a repo with the action enabled. For example, you could iterate directly in master, or in master of a fork. This seems to be a limitation of the fact that CircleCI uses the status (rather than app) API and that this is always tied to the master/default branch of a given repository.

[psobolewskiPhD]

Approved, I think this could be merged as is to see if it resolves the issue -- it won't break anything -- and then can iterate?

[melissawm]

Yeah I think so. Thanks!