mirror of
https://github.com/jesseduffield/lazygit.git
synced 2026-09-10 23:56:24 -04:00
dbb1ff4f24
Bumps [github.com/integrii/flaggy](https://github.com/integrii/flaggy) from 1.4.0 to 1.8.0. - [Release notes](https://github.com/integrii/flaggy/releases) - [Commits](https://github.com/integrii/flaggy/compare/v1.4.0...v1.8.0) --- updated-dependencies: - dependency-name: github.com/integrii/flaggy dependency-version: 1.8.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
18 lines
1.3 KiB
Markdown
18 lines
1.3 KiB
Markdown
# Contributing to Flaggy
|
|
|
|
Thanks for your interest in improving Flaggy! The following guide outlines the standard workflow for proposing and landing a change. Following these steps helps maintainers review contributions efficiently and keeps the project healthy.
|
|
|
|
* **Getting Started**
|
|
- **Open an issue** describing the problem you want to fix or the feature you plan to add. This gives us a chance to discuss the proposal before you start coding.
|
|
- **Fork the repository** to your own GitHub account so you can develop the change independently of the main project.
|
|
* **Implementing Your Change**
|
|
- Make your modifications in your fork (create a topic branch if that helps keep things organized).
|
|
- Add or update tests so your change is well covered.
|
|
- Run the full test suite locally and ensure everything passes (`go test ./...`).
|
|
* **Opening a Pull Request**
|
|
- Push your updates to your fork.
|
|
- Open a pull request against the main repository, referencing the issue created earlier. Include context about what the change does and any testing performed.
|
|
- Participate in the review process and incorporate any requested changes. Keep your branch up to date with the main branch as needed.
|
|
|
|
We appreciate your contributions and look forward to collaborating with you!
|