Projects page: Reconnecting moved or renamed projects (update process)

[diegoguerrad]

Our documentation currently has the following instructions: https://docs.semaphoreci.com/using-semaphore/projects#reconnecting-moved-or-renamed-projects

Based on previous cases, the existing process would be outdated. After a customer updates the name or URL of a repo, we (Semaphore) have to update it on our end for the customer.

We could adjust the steps to have customers reach out through a support ticket with the following details:

• Previous GH repo URL
• New GH repo URL

Before adding any draft, is there any other info we'd need to update a repo URL?

[TomFern]

Created #266 to track the issue.

[diegoguerrad]

hi @TomFern instead of these three bullet points could we ONLY keep the instructions under the "INFO" section?

Those 3 points would no longer be valid - instead customers have to reach out to us to have their repos updated.

[TomFern]

@diegoguerrad I removed the bullet points and left only the info section.

[diegoguerrad]

hi @TomFern thanks for the changes 🙇 but I'm still seeing this section.
We should delete this part which is NO longer valid:

And replace it with this one as the official instructions:

[TomFern]

Sorry, I forgot to push the latest version to prod. It should be fixed in a few hours from now.

[pieterocp]

Eh, tbh I'm only probably the only person on the planet to have moaned about this, might be one to just leave docs a bit broken until this is something the platform just does?

(Well, no idea how painful it is under actually fix it under the bonnet to handle renames, think this is closed source code, but given the folk over at github probably handle it gracefully enough it shouldn't be light years out?)

(But then the dilemma of, do we document what we have, or what we want comes in, and really what we have today is what is used vs what we'd like. Day it's working, then yeah, docs update time 🚀 )