Skip to content
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

Quick question to get this action to work again? #45

Open
adam2392 opened this issue Sep 20, 2023 · 3 comments
Open

Quick question to get this action to work again? #45

adam2392 opened this issue Sep 20, 2023 · 3 comments

Comments

@adam2392
Copy link

Hi,

For some reason I noticed that this Gh action stopped working awhile ago. Now https://github.com/neurodata/scikit-tree/actions/workflows/circle_artifacts.yml shows it is only trigged by codecov(?) but not run?

Here is my workflow file: https://github.com/neurodata/scikit-tree/blob/main/.github/workflows/circle_artifacts.yml
Here is my circleCI docs build file: https://github.com/neurodata/scikit-tree/blob/main/.circleci/config.yml

I'm wondering if you can easily spot something that's not working?

@larsoner
Copy link
Collaborator

Can you check the updated readme in https://github.com/larsoner/circleci-artifacts-redirector-action#example-usage ? I suspect that you're missing some *-token

@adam2392
Copy link
Author

I uploaded a personal token to the repo
Screenshot 2023-09-20 at 10 19 11 AM

and then it seems I specified the right path
Screenshot 2023-09-20 at 10 20 14 AM

However, the action doesn't seem to get triggered: https://github.com/neurodata/scikit-tree/actions/workflows/circle_artifacts.yml

The PR in question I'm playing around w/ is: neurodata/treeple#125

Is it possible that:

  1. There is an issue if codecov is activated?
  2. Does the workflow need to get merged into main first before trying it out on a PR?

@larsoner
Copy link
Collaborator

The PR in question I'm playing around w/ is: neurodata/treeple#125

You cannot test changes in a PR, the action that runs is the one that's in main, see this note in the 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants