4 ms·

Agreed, I'll definitely the ability to move your dependencyci.yml file into a .github folder like the issue and pull request templates: https://github.com/blog/

Agreed, I'll definitely the ability to move your dependencyci.yml file into a .github folder like the issue and pull request templates: https://github.com/blog/2111-issue-and-pull-request-templates https://github.com/blog/2111-issue-and-pull-request-template...

beefsack 10y ago
Except this isn't GitHub specific.
code_research 10y ago
beefsack is right, please do NOT make it a github specific thing. Just one config folder. All config files for services, integration, etc. should go there. Thanks again!
Sir_Cmpwn 10y ago
How about .meta? Hopefully we can encourage github to support this, too. Maybe .meta/github/ could be a thing, too.
- code_research 10y ago
  In the config.rc file you could call that folder however you want. I personally do not like ".meta", because it is not clear what kind of information it may contain. "Meta" might be anything, documentation, description, website, design papers, everything is meta. It is a bit like using "Information" as a menu entry for a website.
  - CiPHPerCoder 10y ago
    It sounds like we should probably all get together and write a draft RFC for this. Choosing a good directory to toss everything into would be grand. I'd prefer .well-known since there's already an RFC for it, but maybe .dev-extra would be more appropriate?
    - robbles 10y ago
      Do you really want to type either of those prefixes thousands of times? Brevity and lack of special chars in the name would be nice to have.
- glenjamin 10y ago
  `.config` is probably a decent choice, as ~/.config for per-user settings seems to be gradually gaining adoption.
- jcassee 10y ago
  Or .well-known? (analogous to https://tools.ietf.org/html/rfc5785 https://tools.ietf.org/html/rfc5785)
tomschlick 10y ago
What about /.bots or /.ci ? Those are specific to these types of services.
happyslobro 10y ago
How about we put each individual config file in its own individual directory? We could name the directory after the file too, so that it is clear where each file is ;) No but seriously, I don't think this mess of config files in the project root is really a big deal. I already grouped the interesting stuff under /src. If it is a big deal, then lets hash out an RFC that covers the general concept of "configuration" once and for all and be done with it.

beefsack 10y ago

Except this isn't GitHub specific.

code_research 10y ago

beefsack is right, please do NOT make it a github specific thing. Just one config folder. All config files for services, integration, etc. should go there. Thanks again!

Sir_Cmpwn 10y ago

How about .meta? Hopefully we can encourage github to support this, too. Maybe .meta/github/ could be a thing, too.

code_research 10y ago
In the config.rc file you could call that folder however you want. I personally do not like ".meta", because it is not clear what kind of information it may contain. "Meta" might be anything, documentation, description, website, design papers, everything is meta. It is a bit like using "Information" as a menu entry for a website.
- CiPHPerCoder 10y ago
  It sounds like we should probably all get together and write a draft RFC for this. Choosing a good directory to toss everything into would be grand. I'd prefer .well-known since there's already an RFC for it, but maybe .dev-extra would be more appropriate?
  - robbles 10y ago
    Do you really want to type either of those prefixes thousands of times? Brevity and lack of special chars in the name would be nice to have.
glenjamin 10y ago
`.config` is probably a decent choice, as ~/.config for per-user settings seems to be gradually gaining adoption.
jcassee 10y ago
Or .well-known? (analogous to https://tools.ietf.org/html/rfc5785 https://tools.ietf.org/html/rfc5785)

tomschlick 10y ago

What about /.bots or /.ci ? Those are specific to these types of services.

happyslobro 10y ago

How about we put each individual config file in its own individual directory? We could name the directory after the file too, so that it is clear where each file is ;) No but seriously, I don't think this mess of config files in the project root is really a big deal. I already grouped the interesting stuff under /src. If it is a big deal, then lets hash out an RFC that covers the general concept of "configuration" once and for all and be done with it.