Contribution Guide
Last updated
Last updated
[[toc]]
Goravel welcomes rich and diverse contributions from different talents, such as coding, translations, articles, tutorials, etc. After completing two enhancements(not containing good first issue), you will be recognized as a core contributor. By completing one enhancement every three months, you can maintain this status. Core contributors will be eligible for benefits when Goravel benefits in the future.
Let's make Goravel more efficient together!
You can report a Bug reports , please search for similar questions before submitting. The report should contains a title and a clear description of the problem, as much relevant information as possible, and a code sample that demonstrates the problem. The goal of the Bug report is to make it easy for yourself and other persons to reproduce the Bug and develop fixes. Goravel encourages committers to create a PR for the Bug repair at the same time, making the open source project more actively developed.
Goravel's GitHub issue trackers are not intended to provide Goravel help or support. Instead, use one of the following channels:
During the development process, if you encounter a problem, you can describe the problem in detail in issue at any time for future communication, but before that, please make sure that you have tried to solve the problem through Google and other methods as much as possible;
Before creating a PR, please improve the unit test coverage as much as possible to provider more stable functions;
When the PR is developed, please add the Review Ready , the maintainer will review in a timely manner.
After the PR is merged, the issue will be closed automatically if the description in the PR is set correctly;
Goravel greatly appreciates your contribution and will add you ro the home contribution list at the next release; ❤️
All bug fixes should be sent to the latest version that supports bug fixes. Bug fixes should never be sent to the master branch unless they fix features that exist only in the upcoming release.
Minor features that are fully backward compatible with the current release may be sent to the latest stable branch.
Major new features or features with breaking changes should always be sent to the master branch, which contains the upcoming release.
Golang v1.18
The minimum version
Provider mock files for unit tests
Goravel artisans
Goravel main repository
Goravel example
Example for Grpc client
The proto dependency of example
Example for package
Document
Goravel Website
The S3 driver of Storage module
The OSS driver of Storage module
The COS driver of Storage module
The Minio driver of Storage module
The Redis driver of Cache module
Providers log splitting functionality for Log module
The Goravel code of conduct is derived from the Laravel code of conduct. Any violations of the code of conduct may be reported to Bowen.
Participants will be tolerant of opposing views.
Participants must ensure that their language and actions are free of personal attacks and disparaging personal remarks.
When interpreting the words and actions of others, participants should always assume good intentions.
Behavior that can be reasonably considered harassment will not be tolerated.
You may propose new features or improvements of existing Goravel behavior in the Goravel framework repository's . Informal discussion regarding bugs, new features, and implementation of existing features takes place in Telegram or Wechat. Bowen, the maintainer of Goravel, is typically present in the group on weekdays from 9am-6pm (UTC+08:00), and sporadically present in the group at other times.
You can find or create an issue in , leave a message to express your willingness to deal with the issue, once confirmed by the repository maintainer, the process can be started.
You can check out if you are new to the process;