git/README.md, branch jch

README: .txt -> .adoc fixes

2025-03-03T21:49:19Z

Signed-off-by: Todd Zullinger Signed-off-by: Junio C Hamano

Merge branch 'jc/majordomo-to-subspace'

2024-01-30T00:03:00Z

Doc update. * jc/majordomo-to-subspace: Docs: majordomo@vger.kernel.org has been decomissioned

Docs: majordomo@vger.kernel.org has been decomissioned

2024-01-20T18:09:07Z

Update the instruction for subscribing to the Git mailing list we have on a few documentation pages. Reported-by: Kyle Lippincott Helped-by: Konstantin Ryabitsev Signed-off-by: Junio C Hamano

doc: switch links to https

2023-11-26T01:07:05Z

These sites offer https versions of their content. Using the https versions provides some protection for users. Signed-off-by: Josh Soref Signed-off-by: Junio C Hamano

Merge branch 'po/readme-mention-contributor-hints'

2022-02-09T22:20:59Z

Doc update. * po/readme-mention-contributor-hints: README.md: add CodingGuidelines and a link for Translators

README.md: add CodingGuidelines and a link for Translators

2022-01-17T19:43:14Z

Before being told how to submit patches, new contributors need to be told how to code for, or how to contribute translation to, the project. Add references to the CodingGuidelines and the README document on localization. Also, split out the instructions to join the list and clarify that subscription is via the majordomo address. We use GitHub Markdown reference [2,3] with trailing empty square brackets, to match existing text in the file. On GitHub/GitLab pages, the footer references matching the empty [] are not shown on the web page. We could switch to using [text](url) form [1] if we wanted to, but that is not done as part of this patch. [1] https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#links [2] https://gist.github.com/ChrisTollefson/a3af6d902a74a0afd1c2d79aadc9bb3f#reference-links [3] https://github.github.com/gfm/#example-561 (and the para aboveit) Signed-off-by: Philip Oakley Signed-off-by: Junio C Hamano

CI: use shorter names that fit in UX tooltips

2021-11-24T00:51:53Z

Change the names used for the GitHub CI workflows to be short enough to (mostly) fit in the pop-up tool-tips that GitHub shows in the commit view. I.e. when mouse-clicking on the passing or failing check-mark next to the commit subject. These names are seemingly truncated to 17-20 characters followed by three dots ("..."). Since a "CI/PR / " prefix is added to them the job names looked like this before (windows-test and vs-test jobs omitted): CI/PR / ci-config (p... CI/PR / windows-buil... CI/PR / vs-build (pu... CI/PR / regular (lin... CI/PR / regular (lin... CI/PR / regular (os... CI/PR / regular (os... CI/PR / regular (lin... CI/PR / regular (lin... CI/PR / dockerized (... CI/PR / dockerized (... CI/PR / dockerized (... CI/PR / static-anal... CI/PR / sparse (pu... CI/PR / documenta... By omitting the "/PR" from the top-level name, and pushing the $jobname to the front we'll now instead get: CI / config (push) CI / win build (push... CI / win+VS build (... CI / linux-clang (ub... CI / linux-gcc (ubun... CI / osx-clang (osx)... CI / osx-gcc (osx) (... CI / linux-gcc-defau... CI / linux-leaks (ub... CI / linux-musl (alp... CI / Linux32 (daald/... CI / pedantic (fedor... CI / static-analysis... CI / sparse (push)... CI / documentation We then have no truncation in the expanded view. See [1] for how it looked before, [2] for a currently visible CI run using this commit, and [3] for the GitHub workflow syntax involved being changed here. Let's also use the existing "pool" field as before. It's occasionally useful to know we're running on say ubuntu v.s. fedora. The "-latest" suffix is useful to some[4], and since it's now at the end it doesn't hurt readability in the short view compared to saying "ubuntu" or "macos". 1. https://github.com/git/git/tree/master/ 2. https://github.com/avar/git/tree/avar/ci-rm-travis-cleanup-ci-names-3 3. https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions 3. https://lore.kernel.org/git/d9b07ca5-b58d-a535-d25b-85d7f12e6295@github.com/ Signed-off-by: Ævar Arnfjörð Bjarmason Signed-off-by: Junio C Hamano

ci: retire the Azure Pipelines definition

2020-04-10T17:30:40Z

We have GitHub Actions now. Running the same builds and tests in Azure Pipelines would be redundant, and a waste of energy. Signed-off-by: Johannes Schindelin Signed-off-by: Đoàn Trần Công Danh Signed-off-by: Junio C Hamano

README: add a build badge for the GitHub Actions runs

2020-04-10T17:30:40Z

Signed-off-by: Johannes Schindelin Signed-off-by: Đoàn Trần Công Danh Signed-off-by: Junio C Hamano

doc: recommend lore.kernel.org over public-inbox.org

2019-11-30T17:12:04Z

Since lore.kernel.org now has the same archive as public-inbox.org and may have more longevity going forward[1], let's recommend people use it for finding or referencing messages. [1] https://public-inbox.org/git/20191120195556.GA25189@dcvr/ or if you like: https://lore.kernel.org/git/20191120195556.GA25189@dcvr/ Signed-off-by: Jeff King Acked-by: Eric Wong Signed-off-by: Junio C Hamano

git/README.md, branch jch

README: *.txt -> *.adoc fixes

Merge branch 'jc/majordomo-to-subspace'

Docs: majordomo@vger.kernel.org has been decomissioned

doc: switch links to https

Merge branch 'po/readme-mention-contributor-hints'

README.md: add CodingGuidelines and a link for Translators

CI: use shorter names that fit in UX tooltips

ci: retire the Azure Pipelines definition

README: add a build badge for the GitHub Actions runs

doc: recommend lore.kernel.org over public-inbox.org

README: .txt -> .adoc fixes