Skip to content

Commit

Permalink
As part of creating new release, get .README.html from docs branch (#291
Browse files Browse the repository at this point in the history
)

Keeping .README.html in each role's root dir would help to have a
consistent README.html in all RHEL versions.
Downstream, we can process this to replace upstream terms.
See RHELPLAN-158622

One concern is that this .README.html is built only as part of GitHub release, so changes made to README.md are not reflected in .README.html until next release, hence for some time .README.html is outdated, that's why it is kept as a hidden file.
  • Loading branch information
spetrosi authored Aug 16, 2023
1 parent 184ba37 commit 9318180
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions role-make-version-changelog.sh
Original file line number Diff line number Diff line change
Expand Up @@ -306,9 +306,10 @@ You have three options:
cat "$rel_notes_file" CHANGELOG.md > .tmp-changelog
fi
mv .tmp-changelog CHANGELOG.md
git add CHANGELOG.md
git show origin/docs:latest/README.html > .README.html
git add CHANGELOG.md .README.html
{ echo "docs(changelog): version $new_tag [citest skip]"; echo "";
echo "Create changelog update and release for version $new_tag"; } > .gitcommitmsg
echo "Update changelog and .README.html for version $new_tag"; } > .gitcommitmsg
git commit -s -F .gitcommitmsg
rm -f .gitcommitmsg "$rel_notes_file" "$new_features_file" \
"$bug_fixes_file" "$other_changes_file" "$pr_titles_file" \
Expand Down

0 comments on commit 9318180

Please sign in to comment.