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

Duplicate Netlify deployment #102

Closed
clementbiron opened this issue Dec 1, 2022 · 1 comment
Closed

Duplicate Netlify deployment #102

clementbiron opened this issue Dec 1, 2022 · 1 comment

Comments

@clementbiron
Copy link
Collaborator

clementbiron commented Dec 1, 2022

Despite the removal of the deploymlent configuration on @Morendil Netlify account we still have duplicate GitHub actions with the identifier thirsty-khorana-a3da09. This is not necessary and could cause problems.

image

We checked with @MattiSG if we could do something with the GitHub repository settings but it doesn't seem to be possible.

@Morendil , would you please contact Netlify support to explain the situation? (I'll take care of it but it seems easier if the message comes from your email address linked to your Netlify account).

You should send them a message via the form available here and the following message (you can obviously change it if you want).

Hello,

Despite the removal of the https://github.com/openfisca/openfisca.org/ repository deployment configuration on my Netlify account, there are still GitHub actions triggered (for exemple in this pull request: https://github.com/openfisca/openfisca.org/pull/97). 

This seems to be a bug on your end as we can't find a way to disable these Netlify actions in the repository settings.

Your help would be greatly appreciated, by replying to this message or in the following issue: https://github.com/openfisca/openfisca.org/issues/102

Thank you.
@MattiSG MattiSG changed the title Duplicate GitHub actions Duplicate Netlify deployment Dec 1, 2022
@MattiSG
Copy link
Member

MattiSG commented Dec 1, 2022

All the duplicate build information disappears when I force push (see #97 and #101). I believe this is thus a misleading information not flushed properly by GitHub in this edge case, but that the disconnection made by @Morendil was actually successful 😃

I'll close this issue, please reopen if the problem reappears!

@MattiSG MattiSG closed this as completed Dec 1, 2022
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