-
Notifications
You must be signed in to change notification settings - Fork 0
Contribution Guidelines
Thank you for your interest in contributing to the Veterans Information Resource! Your help is essential for keeping this project accurate, up-to-date, and useful for our nation's veterans.
This project is open to all, and we welcome contributions of any size, from fixing a typo to improving the core logic of the Preference Advisor.
All contributors are expected to abide by our Code of Conduct. Please be respectful and constructive in all your interactions.
The general workflow for contributing is as follows:
-
Find an Issue: Start by looking at our open issues list. Issues tagged with
good first issueare a great place to start. If you have an idea that doesn't have an issue, please create one first to discuss the change. -
Fork the Repository: Create a personal fork of the project by clicking the "Fork" button in the top-right corner of the repository page.
-
Create a Branch: Create a new branch in your fork for your changes. Use a descriptive name, like
fix/advisor-broken-linkorfeat/add-new-faq-section.git checkout -b your-branch-name
-
Make Your Changes: Edit the files to implement your changes. Be sure to follow our Coding and Content Style Guide.
-
Test Your Changes: Run the site locally to make sure your changes work as expected and don't introduce any new errors. See the Local Development Setup guide for instructions.
-
Commit Your Changes: Write a clear, concise commit message describing what you've done. For example:
docs: Fix typo in VRA guide. -
Submit a Pull Request (PR): Push your branch to your fork and open a Pull Request against the
mainbranch of the original repository. The PR template will guide you through providing the necessary information for a review.
If you have questions about a specific issue or need help getting started, please feel free to comment on the relevant issue or start a new thread in the Discussions tab.