News for hackers. Stuff that matters.

A comment on Introducing unlimited private repositories. Parent comment

Re:Introducing unlimited private repositories by morgante on Wednesday May 11, 2016 @09:55AM (#11675264)
> beware if your open source project needs a single private repository to share passwords

Passwords emphatically do not belong in git.

Your private repos should be maintained such that accessing them would not compromise your security.

[ Parent | on HN ]
Re:Introducing unlimited private repositories by beberlei on Wednesday May 11, 2016 @11:01AM (#11675932)
if you share Ansible inventory files that are encrypted with ansible-vault, then this is not happening. But i still wouldn't want to have a public repository with the files and the metadata of servers that is clearly not meant for public consumption.

Let me brig another example for OSS projects that could need a private repository: branches for security fixes that are not public yet.

[ Parent | on HN ]
Re:Introducing unlimited private repositories by alxndr on Wednesday May 11, 2016 @11:47AM (#11676354)
> "branches for security fixes that are not public yet"

A private git server would probably be better for that, but also wouldn't cost $0.

[ Parent | on HN ]