Update transfer repo instructions to be nodejs/.github-aware#682
Update transfer repo instructions to be nodejs/.github-aware#682
nodejs/.github-aware#682Conversation
| the project. | ||
| - `README.md` | ||
|
|
||
| Ideally, it would not have the following documents to inherit them from |
There was a problem hiding this comment.
I think there was some discussion that when you clone a repo that inherits like this you don't get a copy of the files and that might be a concern.
I don't remember if/where that concern was discussed/addressed but it's probably good to document that it's understood that there will not be copies in case of a clone (unless that has changed or I've got that wrong) and its a choice that we have made on purpose.
@nodejs/tsc any concerns with the code of conduct or contributing files not showing up in a clone?
There was a problem hiding this comment.
You are correct that you do not get a copy of the Code of Conduct checked into the repo.
There was a problem hiding this comment.
At this point, the .github pattern is pretty prevalent and I don't think people expect the files to be always present.
There was a problem hiding this comment.
@ljharb I can understand that, but that is independant from the decision within the project that it's ok not to have a copy in the checked out repo. That is what I thought would be good add to this documentation. That they won't be there AND that the project decided that was ok.
Refs: nodejs/.github#2
Refs: nodejs/.github#3
@nodejs/tsc