Bug with renaming yourself back #23433

munrocket · 2021-06-10T11:32:30Z

munrocket
Jun 10, 2021

Step to reproduce:

create an account
create a public repo
change username (and get some automatic redirection)
try to change it back and get an error

Username change was not successful. The repository name `username1/myrepo` has been retired and cannot be reused

I read documentation about renaming and can’t see that you not allow to rename in back. I think that this is a bug with redirection. But if it’s not here PR in documentation

  <a href="https://github.com/github/docs/pull/7264" target="_blank" rel="noopener nofollow ugc">github.com/github/docs</a>

Documentation about current bug on github

<div class="branches">
  <code>github:main</code> ← <code>munsocket:patch-1</code>
</div>

<div class="github-info">
  <div class="date">
    opened <span class="discourse-local-date" data-format="ll" data-date="2021-06-10" data-time="11:23:30" data-timezone="UTC">11:23AM - 10 Jun 21 UTC</span>
  </div>

  <div class="user">
    <a href="https://github.com/munsocket" target="_blank" rel="noopener nofollow ugc">
      <img alt="munsocket" src="https://user-images.githubusercontent.com/20033246/181076894-91ee80b6-d53b-4eec-adf2-05fc000d8e82.png" class="onebox-avatar-inline" width="20" height="20">
      munsocket
    </a>
  </div>

  <div class="lines" title="1 commits changed 1 files with 1 additions and 1 deletions">
    <a href="https://github.com/github/docs/pull/7264/files" target="_blank" rel="noopener nofollow ugc">
      <span class="added">+1</span>
      <span class="removed">-1</span>
    </a>
  </div>
</div>

Currently you can't rename yourself back.

Step to reproduce:

create an ac…count
create a public repo
change username and get some automatic redirection
try to change it back and get an error

Username change was not successful. The repository name `username1/myrepo` has been retired and cannot be reused

I have a ticket with this bug in contact support #1180808 but if this is expected behavior, this should be in documentation.

<!--
Thank you for contributing to this project! You must fill out the information below before we can review this pull request. By explaining why you're making a change (or linking to a pull request) and what changes you've made, we can triage your pull request to the best possible team for review.

See our CONTRIBUTING.md for information how to contribute.

For changes to content in site policy, see the CONTRIBUTING guide in the site-policy repo.

We cannot accept changes to our translated content right now. See the contributing.md for more information.

Thanks again!
-->

Why:

Closes [issue link]

<!--

If there's an existing issue for your change, please link to it.
If there's not an existing issue, please open one first to make it more likely that this update will be accepted: https://github.com/github/docs/issues/new/choose. -->

What's being changed:

Check off the following:

I have reviewed my changes in staging (look for the deploy-to-heroku link in your pull request, then click View deployment).
For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

This pull request impacts the contribution experience
- I have added the 'writer impact' label
- I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

P.S. Yes I have a ticket #1180808 with this bug in github support but they not answer. Anyone can take my previous name but I am not.

Answered by canuckjacq

Jun 15, 2021

@munsocket if you close the ticket and open a new one, you go to the back of the queue. I am afraid that username tickets may be quite a wait, but closing a ticket isn’t going to help.

View full answer

canuckjacq · 2021-06-11T13:57:18Z

canuckjacq
Jun 11, 2021

👋 Welcome!

I’m afraid that one is going to have to be handled by support. I know it’s been a few days, but it’s in the correct queue and will be handled in order.

0 replies

munrocket · 2021-06-11T16:01:43Z

munrocket
Jun 11, 2021
Author

#1167406 closed created 16 days ago
#1180808 open created 6 days ago

I am closed first ticket because nobody answer in 10 days and created new one 6 day ago. Is there any chance that GitHub Support didn’t see people with new username? But anyway I simply can’t rename myself back but… anybody can do it and take it because login is free.

0 replies

canuckjacq · 2021-06-15T14:44:51Z

canuckjacq
Jun 15, 2021

@munsocket if you close the ticket and open a new one, you go to the back of the queue. I am afraid that username tickets may be quite a wait, but closing a ticket isn’t going to help.

0 replies

munrocket · 2021-06-16T18:11:17Z

munrocket
Jun 16, 2021
Author

Thanks, problem solved!

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitHub Community

Bug with renaming yourself back #23433

{{title}}

Documentation about current bug on github

Why:

What's being changed:

Check off the following:

Writer impact (This section is for GitHub staff members only):

Replies: 4 comments

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

GitHub Community

Bug with renaming yourself back #23433

munrocket Jun 10, 2021

Documentation about current bug on github

Why:

What's being changed:

Check off the following:

Writer impact (This section is for GitHub staff members only):

Replies: 4 comments

canuckjacq Jun 11, 2021

munrocket Jun 11, 2021 Author

canuckjacq Jun 15, 2021

munrocket Jun 16, 2021 Author

munrocket
Jun 10, 2021

canuckjacq
Jun 11, 2021

munrocket
Jun 11, 2021
Author

canuckjacq
Jun 15, 2021

munrocket
Jun 16, 2021
Author