Thank you for contributing to the HullCSS organisation, here are some guidelines to try follow when making changes. If you are unsure as to what to do after reading these please contact the current Webmaster in the HullCSS Discord server. They are found under the @Webmaster role
- Each feature needs to have its own Pull Request (PR)
- Any large changes must be discussed in an Issue first
- If you have owner rights over a repository
- make sure you have GitHub 2FA
- make a new branch for your commits before merging into main, or still please use PRs (unless you are the primary maintainer)
- If possible also gpg sign your commits
- Please see our Security Policy for detais of what to do if you find any issues
- Find the repo you'd like to contribute to.
- Press the fork icon in the top right hand corner.
- Name your fork of the repo
- Press save
Congratulations, you now have created a fork of the repo!
Changes can be made in many different ways in many different ways
- Head to the repo
- Press the pencil icon in the file
- Make changes
- Scroll to the bottom and add a meaningful title and description
- Press commit changes
- Press the green button which says
code - Copy the HTML URL
- Head to VS Code and open a new window
- Choose
Clone Github Repository - Choose where youd like to store the local repo on your machine
- Open the file and make changes
- Press the fork icon on the left side bar
- Enter a message
- Click the tick
- Press sync changes
- Head to your newly changed repo
- Press contribute on the banner above the code
- Press
Open Pull Request - Enter any other details into the input boxes
- Press
Create Pull Request
The GitHub Organisation Managers will look into your commit and may suggest changes. If changes do need to be made, do not make a new pull request, instead just commit to your repo and the new changes will appear.
If no changes need to be made, then your commits will be merged!