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

Issues with this formula being a fork #6

Open
ek9 opened this issue Jan 14, 2017 · 5 comments
Open

Issues with this formula being a fork #6

ek9 opened this issue Jan 14, 2017 · 5 comments

Comments

@ek9
Copy link

ek9 commented Jan 14, 2017

There are a few issues regarding this formula being a linked github fork:

  1. It cannot be found via search ( https://github.com/search?utf8=%E2%9C%93&q=locale+formula )
  2. Any type of contributions on this formula do not show in contributor's activity graphs

The first one being really bad.

It is possible to solve this by one of these steps (depending which one is easiest to accompish for the maintainers of the project):

Solution A: Emailing github support and asking them to unlink the "fork" link. Everything will be the same, we will only loose the "fork from daschatten/locale-fromula" message below the repositories name at the top.

Solution B: Recreate the repository (someone with access to organizatio has to remove this repository, create a new one (NOT doing it by fork) and then push all the contents.

Solution C: Ask if @daschatten plans to maintain his repository and perhaps he can just archive this. I've made an issue on his repository asking what is his stance regarding maintaining his project: daschatten#1

Let me know what you think, I believe this formula would be a lot more popular (user & contribution wise) if it could be found via github at least.

@n-rodriguez
Copy link
Member

@myii WDYT?

@n-rodriguez
Copy link
Member

I would add : you cannot search within the repo :/

@myii
Copy link
Member

myii commented May 27, 2019

@n-rodriguez I found some of these issues in the past but it seems that GitHub has improved at some point so it's not as bad as it used to be. Collecting that in a list, where ticked means it is now solved:

That first issue is still a problem and there could be other implications. Let's raise it in Slack to see what can be done about it.

@myii
Copy link
Member

myii commented May 28, 2019

@n-rodriguez There was a little discussion in Slack about this, starting from here.

@myii
Copy link
Member

myii commented Jun 25, 2019

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

3 participants