Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
64 lines (43 loc) · 1.79 KB

CONTRIBUTING.md

File metadata and controls

64 lines (43 loc) · 1.79 KB
Raw

Contributing Data Updates

This project accepts updates through pull requests (PRs).

What You Can Contribute

  • Add a new cybersecurity / infosec / hacking event entry.
  • Update an existing entry (deadlines, links, city/country, status, notes).
  • Fix formatting or broken links.

Before You Start

  • Make sure you have a GitHub account.
  • Fork this repository (if you do not have write access).
  • Clone your fork locally.

Branch and Edit Workflow

  1. Create a branch:
git checkout -b chore/update-conference-entry

  1. Edit data/conferences.csv per docs/CATALOG.md (schema) and .cursor/skills/update-conference-data/SKILL.md (research rules).

  2. Validate your changes:

    • Check for accidental extra commas or broken CSV rows.
    • Ensure URLs are valid and direct where possible.
    • If unsure about a value, keep TBD / Unknown rather than guessing.

  3. Commit:

git add data/conferences.csv
git commit -m "Update conference entry details"
  1. Push your branch:
git push -u origin chore/update-conference-entry
  1. Open a Pull Request on GitHub.

Pull Request Checklist

  • Clearly state whether you added or updated entries.
  • List affected conference names.
  • Mention key changed fields (for example: deadlines, links, location, status).
  • Note any estimated values and why they were estimated.

Suggested PR Title Format

  • Add: <Conference Name>
  • Update: <Conference Name> deadlines and links
  • Update: multiple conference entries (dates/links/status)

Review Expectations

  • Maintainers may request source verification for critical fields.
  • PRs with uncertain values should keep TBD/Unknown and include notes.
  • Keep changes scoped; avoid unrelated formatting churn.