SrJuggernaut
3f1e80051f
* feat: static site
* feat: mui support & basic theming
* feat: entgamers favicon
* feat: public images until dynamic content can be used
* feat: entgamers & gaming assets
* feat: eslint extra rules
* feat: mui theme modifications
* feat: fontawesome, gsap, bundle analyzer
* feat: common interfaces
* feat: basic layout
* chore: upadted dependencies
* chore: updated dependencies
* feat: updated link styles
* feat: layout now have better interfaces
* feat: basic seo component
* feat: static website
* feat: env variable rules in .gitignore
* feat: added lint to pre-commit
* docs: initial documentation
* ci: deploy using pm2
* ci: pm2 configuration file
* ci: github action deploy preview
* ci: github action deploy production
* ci: env variables now pass to pm2
* fix: pass environment to actions
* feat: post deploy as sudo
* fix: pass only required env to deploy
* revert: deploy as sudo
Refs: 624b225
* fix: server use isomorphic-fetch
* ci: use yarn instead npm
* fix: glass text contrast
* fix: production git ref
* docs: deploy env vars
2.8 KiB
How to contribute
First of all, thank you for taking the time to contribute to the EntGamers project!
The following is a set of guidelines for contributing to the EntGamers website. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
Table of contents
Code of Conduct
This project and everyone participating in it is governed by the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code.
Styleguides
Git Commit Messages
This project uses Commitlint to enforce a consistent commit message format. Please follow the Conventional Commits specification when writing commit messages. This includes merging pull requests.
Pull Request Messages
If the pull request fixes an issue, please include the issue number in the description. As with commit messages, please follow the Conventional Commits specification.
- Use the present tense ("Add feature" not "Added feature")
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- Limit the first line to 72 characters or less
- Reference issues and pull requests liberally after the first line
TypeScript
This project uses ESLint to enforce a consistent code style. Please follow the StandardJS specification when writing TypeScript code.
How Can I Contribute?
Reporting Bugs
- Don't open up a GitHub issue if the bug is a security vulnerability in the website, and instead contact us directly at contacto@entgamers.pro.
- Ensure the bug was not already reported by searching on GitHub under Issues
- If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, steps to reproduce the issue, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
Fixing Bugs
- Look through the GitHub issues for bugs. Anything tagged with "bug" and "help wanted" is open to whoever wants to implement it.
- Fork the repository and create a new branch from
preview. - Make your changes.
- Ensure the changes pass the linter by running
npm run lint. - Submit a pull request.