Skip to content
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

Fix incorrect terminology and grammar in README files #16696

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

Fix incorrect terminology and grammar in README files #16696

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
baeaab2
Update README-branching.md
savvar9991 Mar 4, 2025
1fb868d
Update README-ci-failures.md
savvar9991 Mar 4, 2025
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
2 changes: 1 addition & 1 deletion README-branching.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ The development branches in progress in `mina` are as follows:
- `master`: current stable release, currently mainnet 1.X.
- It is frozen from the crypto side, does not depend on `proof-systems`.
- Never commit to it directly, except to introduce a hotfix.
- `compatible`: scheduled to be softwork released.
- `compatible`: scheduled to be softfork released.
- The staging branch for mainnet soft fork releases.
- It contains all the changes which are literally backwards compatible with the current mainnet deployment. Any nodes running a version of mina based off of compatible should connect to the current mainnet.
- It serves as the preparation ground for the next mainnet soft fork release.
Expand Down
2 changes: 1 addition & 1 deletion README-ci-failures.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ label and comments by MinaProtocol organization members containing exactly
label, please comment on the pull request with `!ci-build-me` to attempt to
re-trigger the script.
If no CI jobs started, check that your membership to O(1) Labs/mina organisation
is public. If your membership is private, the jobs will not started and
is public. If your membership is private, the jobs will not start and
`!ci-build-me` won't have an impact.

If CI jobs are not running after applying both the `ci-build-me` label and
Expand Down