Skip to content

Latest commit

 

History

History
51 lines (36 loc) · 1.99 KB

CONTRIBUTING.md

File metadata and controls

51 lines (36 loc) · 1.99 KB

Contributing Documentation

Thank you for your consideration in contributing to our repo.

To have an effective process, please have a look at our guidelines for contributing.

Notes: If a category doesn't exist for the conference you're suggesting, please feel free to add it to the README.

Tech Conference Categories

Here are the following categories to contribute to:

  • Angular
  • Cybersecurity
  • DevOps
  • General
  • Jamstack
  • Kubernetes
  • React
  • UI/UX
  • Vue

Entry Format

[Conference Name](link to conference website)

Add the conference's description here. This can usually be found on the website's homepage.

Location: City, State, County AND/OR Virtual

Hint: Use an H3 heading for each entry by adding ### followed by a space in front of the Conference Name.

How to Contribute

  1. Check the README to see if your suggestion exists or not.
  2. Fork the repository. Here are the GitHub instructions for forking a repository.
  3. In the command line, clone the repository by typing git clone https://github.com/YOUR-GITHUB-USERNAME/tech-conferences.git
  4. Then type cd tech-conferences to go into the project's directory.
  5. Create a branch and switch to that new branch by using the following command: git checkout -b new-branch-name
  6. Update the README.md with your conference suggestion(s).
    • Append the title and link to the conference, to the list in the appropriate category
  7. In the command line, stage your changes by using the git add . command.
  8. Commit your changes by using the git commit -m "commit message" command.
  9. Push up your changes to the remote branch on GitHub by using the git push -u origin branch_name command.
  10. Open a PR directed to our main branch.
  11. The maintainers will review your PR and either request changes or approve it.

Beginner Friendly Resources for Using Git and GitHub