Skip to content

Fix documents relating on github #1

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.

Sign up for GitHub

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

Merged
Currypan1229 merged 2 commits into from
Feb 8, 2026
Merged

Fix documents relating on github #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f19fde2
Fix content of CONTRIBUTING.md
Currypan1229 Feb 8, 2026
5d2847c
Fix url of Build Status badge in README.md
Currypan1229 Feb 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions .github/CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,17 +44,17 @@ If you would like to suggest a new feature:
### Getting Started

1. Fork the repository and create a new branch for your development work.
- If your changes are **backward compatible**,
open a PR targeting the main branch (commonly named `main` or`master`).
- If your changes **are not backward compatible**,
open a PR targeting the development branch (commonly named `dev` or `develop`).
- If your changes are **backward compatible**,
open a PR targeting the main development branch (commonly named `dev` or `develop`).
- If your changes **are not backward compatible**,
open a PR targeting the development branch (commonly named `dev2` or `develop2`).
2. Keep your changes minimal and focused.
- Large or unrelated changes in a single PR are discouraged, as they are more likely to conflict with other work.
- Large or unrelated changes in a single PR are discouraged, as they are more likely to conflict with other work.
3. Follow the coding style and run tests before submitting.
- This is **very important**. Please refer to the [Code Requirements](#code-requirements) section below.
- This is **very important**. Please refer to the [Code Requirements](#code-requirements) section below.
4. Once your changes are ready, push your branch and open a Pull Request.
- If your PR meets the requirements, it will eventually be merged.
- It may take some time—please be patient and check back occasionally.
- If your PR meets the requirements, it will eventually be merged.
- It may take some time—please be patient and check back occasionally.

---

Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Service Library for Rust

[![Build Status](https://github.com/Akazukin-Team/Rust-Service-Library/actions/workflows/build.yml/badge.svg?branch=main)](https://github.com/Akazukin-Team/Rust-Service-Library/actions/workflows/build.yml?query=branch:main)
[![Build Status](https://github.com/Akazukin-Team/Rust-Service-Library/actions/workflows/build.yml/badge.svg)](https://github.com/Akazukin-Team/Rust-Service-Library/actions/workflows/build.yml?query=branch:main)

A library providing manager for many similar services.

Expand Down