Skip to content

update workflow, no more special color handling #566

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

Closed
wants to merge 4 commits into from

Conversation

dajmcdon
Copy link
Contributor

Checklist

Please:

  • Make sure this PR is against "dev", not "main" (unless this is a release
    PR).
  • Request a review from one of the current main reviewers:
    brookslogan, nmdefries.
  • Makes sure to bump the version number in DESCRIPTION. Always increment
    the patch version number (the third number), unless you are making a
    release PR from dev to main, in which case increment the minor version
    number (the second number).
  • Describe changes made in NEWS.md, making sure breaking changes
    (backwards-incompatible changes to the documented interface) are noted.
    Collect the changes under the next release number (e.g. if you are on
    1.7.2, then write your changes under the 1.8 heading).
  • See DEVELOPMENT.md for more information on the development
    process.

Change explanations for reviewer

Magic GitHub syntax to mark associated Issue(s) as resolved when this is merged into the default branch

  • Resolves #{issue number}

pkgdown::clean_site(pkg)
pkgdown::build_site(pkg, preview = FALSE, install = FALSE, new_process = FALSE)
pkgdown:::build_github_pages(pkg)
run: pkgdown::build_site_github_pages(new_process = FALSE, install = FALSE)
Copy link
Contributor

@dshemetov dshemetov Nov 12, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So all the previous code was there to trigger dev docs for the dev branch, rather than basing it on x.y.z.9000 version numbers. I honestly would prefer to move to the latter, default model, but we'll need to adjust our workflows a bit. @dsweber2

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll bring this back. I don't think there's a way to change with the dev branch unfortunately. But hopefully we don't need the color handling any more.

@dajmcdon dajmcdon requested a review from dshemetov November 13, 2024 17:14
@brookslogan
Copy link
Contributor

I let this sit too long and am going to just release dev -> main so we should get the updates from that.

@brookslogan brookslogan closed this Dec 9, 2024
@dshemetov dshemetov deleted the delphidocs-main branch December 14, 2024 00:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants