GitHub deployments are out of synchronisation with Fly.io

[Jiralite]

I have connected my GitHub repository with my Fly.io application. I connected it to the wrong repository at first, so I severed the connection and connected it to the right one. Now, I have a deployment on GitHub that looks like that it will run forever:

For context, it takes about a minute to deploy this application.

Upon connecting to the correct repository and pushing a commit, nothing happened, so I went to Fly.io which said I needed to press launch because I changed repositories. I did so, and that triggered a new deploy which finished in about a minute. Fly.io is good:

However, GitHub is not:

I saw a button that additional configuration files were necessary for me to pull request. I clicked the pull request button, and it gave an error stating the branch was not present or something.

I opened my deployments tab after and got this wonderful error:

Something sounds wrong here.

Tried a commit and it doesn’t trigger the deploy. Going back to GitHub Actions for now, but would appreciate this being looked into.

[jphenow]

Hey I’m taking a look at what’s wrong here.

Out of curiosity are you able to try disconnecting and reconnecting GitHub?

You should be able to do so here: Sign in to Your Account · Fly

Edit: Also, do you see Fly.io in your GitHub apps if you go to your GitHub repository => “Settings” => “GitHub Apps”?

[Jiralite]

I have just now disconnected and reconnected GitHub per that link.

I do see Fly.io in my GitHub applications for my repository:

Since disconnecting and reconnecting GitHub, it hasn’t triggered a deployment. It is connected in Fly.io though:

The old deployments are still ongoing too. Not sure what to do about these:

[jphenow]

Yea it seems like there’s technically a way they can wind up appearing to hang on GitHub’s side (they likely aren’t actually). I think we somehow lose authorization or fail to auth to GitHub to update somewhere in your case.

From my end for your dashboard issues, it looks to be the same, we’re expecting access to GitHub where we don’t have it.

It’s weird we were able to create those deployments but then it can’t mark them complete.

Out of curiosity, do you see anything in Configure (next to the Fly.io GitHub App in GitHub) that would indicate we don’t have access to the repo you’re referring to? Or perhaps some notes about accepting new permissions?

[Jiralite]

thatskyapplication/website is part of the thatskyapplication organisation. The application is installed to the organisation with specific access to thatskyapplication/website only:

I don’t see an indication here to accept or adjust permissions.

[jphenow]

Weird question perhaps, possible it doesn’t even apply to you.

If you look at your Repo in GitHub. Is it marked as “internal” or is it “private”?

[Jiralite]

Sadly doesn’t apply as this is not an enterprise account. It’s just private.

[jphenow]

OK I think we’re closer to narrowing down what all is going on.

I forgot you mentioned you switched repos on the app. It looks like you have multiple apps hooked to that same repo.

Can you confirm for us which app is not working? Is the other one working?

[jphenow]

I have an imperfect fix that is finishing up deploying right now.

Could you try navigating to that app and drop a note about how it’s working for you?

[Jiralite]

Fly.io thatskyapplication-website → GitHub thatskyapplication/website
Fly.io caelus → GitHub thatskyapplication/caelus

Initially, I connected thatskyapplication/website (GitHub) to caelus (Fly.io) by mistake. I then correctly switched it over to thatskyapplication-website (Fly.io).

thatskyapplication/caelus (GitHub) does not have the Fly.io application:

I cannot verify what’s going on in Fly.io because the overview and deployments are 500’ing for caelus (Fly.io) and have been for 3-4 days (see my other post).

[Jiralite]

Oh my gosh. I can finally load Caelus on Fly.io!