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

ci: use FAST_FORWARD_TOKEN to query api in fast-forward.yml #3137

Merged

Conversation

BacLuc
Copy link
Contributor

@BacLuc BacLuc commented Nov 5, 2022

@BacLuc
Copy link
Contributor Author

BacLuc commented Nov 5, 2022

Sorry, colossal fail by me.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 62.334% when pulling bd101ba on BacLuc:ci-fast-forward-use-token-to-fetch-api into 639f4a8 on ecamp:devel.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 62.334% when pulling bd101ba on BacLuc:ci-fast-forward-use-token-to-fetch-api into 639f4a8 on ecamp:devel.

Copy link
Member

@usu usu left a comment

Choose a reason for hiding this comment

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

🤣 okee, I didn't thought about checking the code line-by-line

I noticed that the secret was never used, but didn't thought much more as it was only used during the actual fast-forward merge (which never happened...)

Happy if this solves it.

But I'd say not fail to you but fail to Github API docu. Not nice to have an undocumented property that then changes values based on who sends the query.

@carlobeltrame carlobeltrame merged commit ae3b4ce into ecamp:devel Nov 6, 2022
@BacLuc BacLuc deleted the ci-fast-forward-use-token-to-fetch-api branch November 6, 2022 13:13
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.

4 participants