Expand CONTRIBUTING.md to help new contributors #1516
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1516
Loading…
Reference in New Issue
No description provided.
Delete Branch "unknown repository"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Installation, building, file/directory structure, submitting patches
Rendered - https://github.com/dawidpotocki/privacytools.io/blob/contributing/CONTRIBUTING.md
Deploy preview for privacytools-io ready!
Built with commit 4f9b9cddd48d451d678ce305947d45496bdeaa64
https://deploy-preview-1516--privacytools-io.netlify.com
Deploy preview for privacytools-io ready!
Built with commit
2219b5d634
https://deploy-preview-1516--privacytools-io.netlify.com
Why are you moving the file from .github/CONTRIBUTING.md to CONTRIBUTING.md which prevents seeing a clean diff?
How about first you do the changes you wish and in another PR rename the file if you have a very good reason of doing that?
I agree it doesn’t make sense to me to move repo files out of
.github
.And for me it makes crap ton of sense. CONTRIBUTING.md is not GitHub
specific. Just like we have README.md and LICENSE.txt at the root of
repository, even though they can be placed in
.github
. It makes iteasier to find, because it was before in a hidden directory, for which
I'm never looking for when I clone the project and it will still be
detected by GitHub. I don't see a reason for it staying there.
Your headers don't match your table of contents, and therefore the links won't work. Also, not sure why you are using hard text wrapping and
instead of Markdown's double-newline for line breaks.
@privacytools/editorial I removed Dawid's assignment to this, should we still continue with it ourselves?
I guess so, I haven't looked into it in too much detail.