Thank you for your interest in contributing to LangTest! We value the contributions of our community members and are excited to have you on board. To make the development journey smooth and collaborative, please adhere to the following steps:
- Thoroughly review the guidelines provided below.
- If you're eager to add a new feature to the LangTest library, navigate to the documentation for a clear understanding.
- To illustrate the process, we've included a simple example in the documentation to guide you.
-
Explore Our Issues: Browse through our list of open issues on the Issues tab. These issues cover a wide range of topics and difficulties. You might find something that aligns with your skills and interests.
-
Filter and Search: Use the provided labels and filters to narrow down the list of issues. You can filter by tags like
feature
,bug
,fix
, etc. Also, utilize the GitHub search bar to look for keywords related to your expertise. -
Read and Understand: Once you've found an issue that captures your attention, take a moment to thoroughly read and understand it. Make sure you comprehend the problem, the expected solution, and any existing discussion around it.
-
Clarify Doubts: If you have any questions or need further clarification, don't hesitate to comment on the issue. Our community is friendly and always willing to help. It's better to seek clarity before diving in.
-
Claim the Issue: If you feel confident about tackling the issue, leave a comment expressing your intention to work on it. This prevents duplication of efforts and allows us to provide guidance if needed.
-
Understand Contribution Guidelines: Familiarize yourself with our Contribution Guidelines. This document outlines coding standards, pull request procedures, and other important details.
Fork this repository by clicking on the fork button on the top of this page. This will create a copy of this repository in your account.
Now clone the forked repository to your machine. Go to your GitHub account, open the forked repository, click on the code button and then click the copy to clipboard icon.
Open a terminal and run the following git command:
git clone "url you just copied"
where "url you just copied" (without the quotation marks) is the url to this repository (your fork of this project). See the previous steps to obtain the url.
For example:
git clone https://github.com/username/langtest.git
where username
is your GitHub username.
Change to the repository directory on your computer (if you are not already there):
cd langtest
Now create a branch using the git checkout -b
command:
git checkout -b your-branch-name
-
Set Up Environment: Create a virtual environment for LangTest using your preferred method. For example, you can use
venv
orconda
.
Poetry is the package manager used for this project. If you don't have Poetry installed, run the following command:
pip install poetry
Use Poetry to install the project dependencies:
poetry install --with dev
Add those changes to the branch you just created using the git add
command:
git add .
Now commit those changes using the git commit
command with a meaningful message:
git commit -m "Add feature: feature-name"
Push your changes using the command git push
:
git push -u origin your-branch-name
replacing your-branch-name
with the name of the branch you created earlier.
If you go to your repository on GitHub, you'll see a Compare & pull request
button. Click on that button.
Create a pull request (PR) from your forked repository to the main LangTest repository.
- Clearly describe the changes you've made and the issue it addresses in the PR description.
- If the PR is related to an existing issue, mention it using the syntax "Fixes #issue_number."
For pull request template click here
Our team will review your pull request, provide feedback, and work with you to ensure that your contribution meets the project's guidelines and quality standards
- If you have an idea for a new feature, improvement, or bug fix, you can propose a new issue.
- Go to the Issue Tracker and click on "New Issue" or just create a new issue from here
- Choose the appropriate issue lables (feature, fix, bug, etc.).
- Provide a clear and concise title and description of the proposed issue.
- Add labels and assignees, if applicable, to help categorize and track the issue.
We're excited to have you on board with us! Together, we can make NLP models safer, more reliable, and fairer for everyone.
Congrats! You just completed the standard fork -> clone -> edit -> pull request workflow that you'll often encounter as a contributor!
Celebrate your contribution and share it with your friends and followers by going to LinkedIn
You can join our community team if you need any help or have any questions.
- Slack For live discussion with the LangTest community, join the
#langtest
channel - GitHub For bug reports, feature requests, and contributions
- Discussions To engage with other community members, share ideas, and show off how you use LangTest!
We would like to acknowledge all contributors of this open-source community project.
LangTest is released under the Apache License 2.0, which guarantees commercial use, modification, distribution, patent use, private use and sets limitations on trademark use, liability and warranty.