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
.
Here are the following categories to contribute to:
- Angular
- Cybersecurity
- DevOps
- General
- Jamstack
- Kubernetes
- React
- UI/UX
- Vue
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
.
- Check the
README
to see if your suggestion exists or not. - Fork the repository. Here are the GitHub instructions for forking a repository.
- In the command line, clone the repository by typing
git clone https://github.com/YOUR-GITHUB-USERNAME/tech-conferences.git
- Then type
cd tech-conferences
to go into the project's directory. - Create a branch and switch to that new branch by using the following command:
git checkout -b new-branch-name
- Update the
README.md
with your conference suggestion(s).- Append the title and link to the conference, to the list in the appropriate category
- In the command line, stage your changes by using the
git add .
command. - Commit your changes by using the
git commit -m "commit message"
command. - Push up your changes to the remote branch on GitHub by using the
git push -u origin branch_name
command. - Open a PR directed to our
main
branch. - The maintainers will review your PR and either request changes or approve it.