docs: add BreakingChanges to TECH_DOCS target
Subsystems (2)
PATCH 1/1 docs: add BreakingChanges to TECH_DOCS target
From: Phillip Wood <[email protected]>
When BreakingChanges.txt was added in 57ec9254eb9 (docs: introduce document to announce breaking changes, 2024-06-14) there was no corresponding change to the Makefile to build it. Fix that by adding it to the TECH_DOCS target.
---
docs: add BreakingChanges to TECH_DOCS target
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1921%2Fphillipwood%2Fbuild-breaking-changes-docs-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1921/phillipwood/build-breaking-changes-docs-v1
Pull-Request: https://github.com/git/git/pull/1921
Documentation/Makefile | 1 + Documentation/meson.build | 1 + 2 files changed, 2 insertions(+)
Documentation/Makefile +1 -0
@@ -109,6 +109,7 @@ SP_ARTICLES += howto/coordinate-embargoed-releases API_DOCS = $(patsubst %.adoc,%,$(filter-out technical/api-index-skel.adoc technical/api-index.adoc, $(wildcard technical/api-*.adoc))) SP_ARTICLES += $(API_DOCS) +TECH_DOCS += BreakingChanges TECH_DOCS += DecisionMaking TECH_DOCS += ReviewingGuidelines TECH_DOCS += MyFirstContribution
Documentation/meson.build +1 -0
@@ -440,6 +440,7 @@ if get_option('docs').contains('html') ) articles = [ + 'BreakingChanges.adoc', 'DecisionMaking.adoc', 'MyFirstContribution.adoc', 'MyFirstObjectWalk.adoc',
base-commit: 683c54c999c301c2cd6f715c411407c413b1d84e
Signature · 1 line
gitgitgadget
Quoted 6 lines · Phillip Wood via GitGitGadget
From: Phillip Wood <[email protected]>
When BreakingChanges.txt was added in
57ec9254eb9(docs: introduce document to announce breaking changes, 2024-06-14) there was no corresponding change to theMakefileto build it. Fix that by adding it to theTECH_DOCStarget.
Makes sense, thanks for this improvement!
Patrick