Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

Problem

  • Today there is no setting to remove the "generated from" repo tag.
  • The "generated from" tag looks exactly like "forked from" so it looks unprofessional.

Potential solution

Give users the option to remove the "Generated from <source_repo>" from the repo from the settings k.

Screenshot 000217@2x

Around the web

You must be logged in to vote

Replies: 103 comments · 19 replies

Comment options

I'm wondering if it's at least possible to remove it by contacting GitHub support?

You must be logged in to vote
1 reply
@Hackx2
Comment options

sadly, it isn't.

Comment options

It would be great if it were possible to remove it. I have a repository that was generated from a template years ago, but it does not resemble the template anymore at all, making the "generated from" kinda misleading and a lie about the current situation.

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

The templates should help people to spin up their project quickly. However, templates are relatively barebone and therefore should not dangle around forever if at all, unlike forks that add true informational value. At first, the template tag link may be useful by providing the developer a shortcut to access the template documentation, but after the project is set up, the template tag is just extra clutter.

Personally I feel the tag makes the project look a bit "cheap". Currently, to avoid this feel and look, I need to copy the template files manually to the new project, thus nullifying the purpose of the Template feature in the first place.

Please GitHub, just make it optional for the repo maintainer to show the tag, just in the way the maintainer can currently hide Issues, Wiki, and Projects.

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1
My devs are asking for this too

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
1 reply
@LISA-KOREA

This comment was marked as off-topic.

Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

It's a bit of an annoying workaround, but I was able to get rid of the "generated from" tag directly from the Github web UI. (Note: same as the solution in the stack overflow post, this will not preserve PRs, issues, etc.) Steps:

  • Click "use this template" and create a new repo from it as normal
  • Mark the new repo (which contains the "generated from" tag) as a template repository in settings
  • From the repo you just created click "use this template" and create another new repo
  • Delete the first repo you created (parent of the one in the last step) and the tag should disappear from the child
You must be logged in to vote
3 replies
@fiddlermikey
Comment options

That is an interesting workaround, and you're right, kind-of annoying too. lol This wouldn't be too bad for an individual dev, but not really good for most orgs with multiple devs.

A+ for creativity.

@aiadam36
Comment options

You've saved my whole career. Big Thanks!

@mrlubos
Comment options

This is what IQ140 looks like

Comment options

I found another way, although maybe not perfect. If the template repo is your own, you can delete the template repo first, so that this tag will disappear.

You must be logged in to vote
1 reply
@drl990114
Comment options

The current effective solution can be found here: https://stackoverflow.com/a/76436754/16346493

Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

So far, as Github seems not in a hurry with addressing that specific point, the simple preventive steps still working well is again:

  • Don't use the "Use this Template" button to create a repo
  • Clone it directly, create a blank repo and replace the origin remote
  • You end up with the same starting point, but no "Generated with X"
  • Giving initial credit to the Template is still possible in the README
You must be logged in to vote
1 reply
@VelocityRa
Comment options

This is not enough for some templates that contain post-processing via GitHub Actions, like https://github.com/cpp-best-practices/cmake_template.
In that case you need to create a temporary repo, get the contents and paste them in your repo.

Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1

Funny that if you ask Github Copilot, it hallucinates that there's an option to detach from template in Repo Settings

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

why is this still an issue GitHub....
I wouldn't even mind if it was less prominent but it's literally in full view of everyone who views it

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Comment options

+1

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Repositories The core of version-controlled code storage General General topics and discussions that don't fit into other categories, but are related to GitHub
Morty Proxy This is a proxified and sanitized view of the page, visit original site.