We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We’re excited you’re interested in contributing! Please follow these steps to ensure a smooth and efficient collaboration process.
Clone the forked repository to your local machine by running the following command:
git clone https://github.com/YOUR_USERNAME/REPOSITORY_NAME.git
Replace YOUR_USERNAME and REPOSITORY_NAME with your GitHub username and the repository name.
YOUR_USERNAME
REPOSITORY_NAME
Follow branch naming conventions outlined in the Git Guidelines.
Create a branch name based on the type of change (e.g., feat/name-related-issue, fix/name-related-issue).
feat/name-related-issue
fix/name-related-issue
git checkout -b branch-name
Example: feat/update-readme or fix/login-bug.
feat/update-readme
fix/login-bug
Make changes in your local repository.
Follow atomic commit principles:
git add . git commit -m "type(scope): description"
Examples:
feat(authentication): add support for OAuth login
fix(api): resolve 404 error in user endpoint
docs(readme): update contribution guidelines
Push your changes to your forked repository:
git push origin your-branch-name
⚠️ Note: This repository uses Husky for pre-push hooks. Husky will automatically run npm run format and npm run lint before allowing the push.
npm run format
npm run lint
main
⚠️ Important: Pull requests without the proper template or missing required details may be rejected.
Thank you for contributing! 🚀✨
The text was updated successfully, but these errors were encountered:
No branches or pull requests
🌟 Contributing Guide | SafeTrust
We’re excited you’re interested in contributing! Please follow these steps to ensure a smooth and efficient collaboration process.
1️⃣ Fork the Repository
2️⃣ Clone the Fork
Clone the forked repository to your local machine by running the following command:
Replace
YOUR_USERNAME
andREPOSITORY_NAME
with your GitHub username and the repository name.3️⃣ Create a New Branch
Follow branch naming conventions outlined in the Git Guidelines.
Create a branch name based on the type of change (e.g.,
feat/name-related-issue
,fix/name-related-issue
).4️⃣ Make Changes and Write Atomic Commits
Make changes in your local repository.
Follow atomic commit principles:
feat(authentication): add support for OAuth login
fix(api): resolve 404 error in user endpoint
docs(readme): update contribution guidelines
5️⃣ Run the Project Locally
6️⃣ Push Your Changes
Push your changes to your forked repository:
npm run format
andnpm run lint
before allowing the push.7️⃣ Create a Pull Request (PR)
main
of the original repository.💡 Additional Notes
Thank you for contributing! 🚀✨
The text was updated successfully, but these errors were encountered: