-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
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
CONTRIBUTORS GUIDELINE 🧪 #34
Comments
This was referenced Dec 12, 2024
6 tasks
This was referenced Jan 22, 2025
This was referenced Jan 24, 2025
This was referenced Jan 26, 2025
This was referenced Jan 28, 2025
This was referenced Feb 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🌟 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: