-
Notifications
You must be signed in to change notification settings - Fork 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.
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
V1.1 #81
Open
tviegut
wants to merge
29
commits into
master
Choose a base branch
from
v1.1
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit backmerges the PDF generation, enumerated headings, GitHub Action, README notes, and other useful peripheral artifacts for maintaining the CIM Modeling Guide via GitHub and mkdocs. The 'master' branch had all the correct configuration that just needed to be backmerged to the v1.1 branch.
Adds GitHub Action that you can to publish version 1.1 of the https://cim-mg.ucaiug.io website. This isn't done autmomatically on merge but rather manually/on-demand by navigating to the "GitHub Action" tab of the repo and running it. This is manual so that the CIM Modeling Guide maintainers have full control over when new versions get published.
The default color styling used for the PDF included red underlines and a light grey color for hyperlinks which made them hard to see. This update changes the red underlines to use CIM color scheme (#009dab) and changes hyperlinks to familiar blue color.
The GitHub Action workflow for publishing the site was failing. This is due to the gh-pages branch not getting checked out on GitHub Action runs. It does not get checked out because by default the actions/checkout@v4 step does a very lightweight checkout (i.e. only current branch with depth of 1). This commit adds a fetch of the gh-pages branch so that the branch is checked out and the publish step does not report missing remote changes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.