Skip to content
This repository has been archived by the owner on Nov 29, 2017. It is now read-only.

Rename repository to eg. jekyll-help #17

Closed
mscharley opened this issue Apr 14, 2014 · 17 comments
Closed

Rename repository to eg. jekyll-help #17

mscharley opened this issue Apr 14, 2014 · 17 comments

Comments

@mscharley
Copy link

People who are watching via emails get a tag in the subject line of [help] where the repository name is. This isn't terribly helpful, renaming the repo while it's still in it's infancy could help people out a lot long-term.

@troyswanson
Copy link
Member

👍 Good idea!

@mscharley
Copy link
Author

/cc @parkr

@ndarville
Copy link

Ahh, good observation. Guess that forces our hand?

@parkr
Copy link
Member

parkr commented Apr 14, 2014

Do you think many people are subscribed to more than one help repo? I really like the cleanliness of the URL. @benbalter is there a way to change this on the user's end, like get NWO (e.g. [jekyll/help]) in the subject line?

@mscharley
Copy link
Author

@parkr You're probably right in that there's not many other */help repos, however you've also advocated people forking the repo to share code. If I were to fork jekyll/help I would create mscharley/help by default. Somewhat less desirable and far less useful.

@troyswanson
Copy link
Member

Coming from GitHub, a simple [help] doesn't really provide enough context. I agree that it's clean, but we shouldn't expect users to modify settings in order for them to know that it's Jekyll they're getting help with.

@albertogg
Copy link
Member

☝️ what @troyswanson said.

@ndarville
Copy link

Ideally, we want people to see how well Jekyll Help works and do the same with their projects, so in a perfect world, we’d have a “namespacing” issue, as Jekyll Help shoots to stardom. :)

@mattr-
Copy link
Member

mattr- commented Apr 15, 2014

I do love the cleanliness of the URL. I don't feel like filtering on a subject of '[help]' when GitHub provides proper List-Id headers for it's emails is a valid reason to change the repo. That said, plenty of us don't filter our email at all, so I'd be fine with a repo rename to jekyll-help.

@doktorbro
Copy link
Member

@benbalter is there a way to change this on the user's end, like get NWO (e.g. [jekyll/help]) in the subject line?

I would love to see it. I wonder since day one here why Github doesn’t put user’s name in the subject line.

@mscharley
Copy link
Author

User names are in the From header, not really any need to put it in the
subject line as well.

On 21 April 2014 05:20, Anatol Broder notifications@github.com wrote:

@benbalter https://github.com/benbalter is there a way to change this
on the user's end, like get NWO (e.g. [jekyll/help]) in the subject line?

I would love to see it. I wonder since day one here why Github doesn’t put
user’s name in the subject line.


Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-40902547
.

@doktorbro
Copy link
Member

@mscharley, I mean the user name from the repository owner. It’s "jekyll" here. Github could add it as namespace:

Re: [jekyll/help] Rename repository to eg. jekyll-help (#17)

But now I see, the To-field is already namespaced: jekyll/help <help@noreply.github.com>. So you can already identify the sender.

@mscharley
Copy link
Author

Except that email apps rarely show the to field in listings, it was clearly
to me, it's in my inbox.

On 21 April 2014 05:35, Anatol Broder notifications@github.com wrote:

@mscharley https://github.com/mscharley, I mean the user name from the repository
owner
. It’s "jekyll" here. Github could add it as namespace:

Re: [jekyll/help] Rename repository to eg. jekyll-help (#17)

But now I see, the To-field is already namespaced: jekyll/help <
help@noreply.github.com>. So you can already identify the sender.


Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-40902893
.

@troyswanson
Copy link
Member

What do we want to do here? I vote for changing it. Either way, we should decide something. 😄

@albertogg
Copy link
Member

I vote for changing it too.

@parkr
Copy link
Member

parkr commented Apr 29, 2014

It makes me sad to see the redundancy, but it's done. Hopefully this clears up your inboxes!

@parkr parkr closed this as completed Apr 29, 2014
@troyswanson
Copy link
Member

@parkr I agree, dude. It's better now, though. Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants