Repository navigation
Merge master (v0.1.0) into develop - #3
Merged
Merged
Conversation
Documenter pages for the package, the reference of the hand-written functions, and the command builders, with every subcommand's docstring. The documentation is a project of the workspace, beside the tests. The README links the stable and development documentation.
After BioJuliaTemplate.jl: - unit tests on Julia 1.12, the latest release and nightly, on Linux, macOS and Windows, with Codecov coverage; - the documentation, built on pull requests and deployed from `develop` and tags; - Runic formatting; - Dependabot for the compat of the workspace's projects and the versions of the actions. The actions are pinned to commits, with their versions in comments, which Dependabot updates.
Issue and pull request templates, funding, and TagBot, which tags releases registered in the General registry. The README's Contributing section points to BioJulia's contributing guidelines, semantic versioning and the changelog.
The Gitflow workflow calls the shared checks on pull requests into master and develop: the source branch, the version, the changelog and its comparison links, breaking changes, and the changelog entry. The Back-merge workflow opens the pull request that brings master back into develop once a release or hotfix merges, with the ReleaseFlow app's credentials from the `releaseflow` environment. Both name master as the main branch. CODEOWNERS requires a maintainer's review of the workflows, and Dependabot labels its updates of the actions `skip changelog`. The README's Contributing section and the pull request template describe the branching model.
The changelog's unreleased entries move into the section of 0.1.0, with the comparison links.
This branch was successfully deployed
This file contains hidden or 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
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.
This brings master back into develop after the release or hotfix of v0.1.0, as gitflow does.
If it conflicts with develop, merge develop into back-merge/v0.1.0, resolve the conflicts there, and push.