[go: up one dir, main page]

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

Removing need for GH_ACCESS_TOKEN #168

Merged
merged 1 commit into from
Dec 17, 2021
Merged

Removing need for GH_ACCESS_TOKEN #168

merged 1 commit into from
Dec 17, 2021

Conversation

galleon
Copy link
Contributor
@galleon galleon commented Dec 16, 2021

The token was not in the secrets which causes this job to break.
The secret is not referenced anymore

Copy link
Contributor
@nhuet nhuet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am pretty sure it is working, but did you test it (=the new release wf) on a tag on your fork? Can you add a link to the corresponding run if it is the case?
Thanks !

(If i were picky, i would point out that we would rather have first line of commit line be in imperative mood :)

@galleon
Copy link
Contributor Author
galleon commented Dec 17, 2021

It was tested live: https://github.com/airbus/scikit-decide/runs/4551726615?check_suite_focus=true. On my repo I have a secret :-) but it is not needed ... It was removed everywhere but this one was forgotten.

@galleon galleon merged commit b60b714 into airbus:master Dec 17, 2021
@galleon galleon deleted the gal/fix_release branch December 17, 2021 12:35
@nhuet
Copy link
Contributor
nhuet commented Dec 17, 2021

Hum... When following your link, i see a workflow crashing 😅 :

Error: Unhandled error: Error: Input required and not supplied: github-token

So it seems not working actually ?

@nhuet
Copy link
Contributor
nhuet commented Dec 17, 2021

Ok, i understand now, the link was pointing to the airbus repo (and not @galleon 's fork) and to the release occuring before this PR. So the link was explaining why the PR is needed.
Personnally i would have tested with a fake release on my fork with this commit to be sure, but it is ok for now.

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

Successfully merging this pull request may close these issues.

3 participants