Bump external/pipeline-Nextflow-config from da8e990 to 3ec7186
#22
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
the
dependencies
dependabot
bot
requested review from
tyamaguchi-ucla,
yashpatel6,
sorelfitzgibbon and
a team
as code owners
|
@dependabot rebase |
dependabot
bot
force-pushed
the
dependabot/submodules/external/pipeline-Nextflow-config-3ec7186
branch
from
d1c56e3
to
9d91432
Compare
|
@dependabot rebase |
|
Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request |
|
@dependabot recreate |
Bumps [external/pipeline-Nextflow-config](https://github.com/uclahs-cds/pipeline-Nextflow-config) from `da8e990` to `3ec7186`. - [Release notes](https://github.com/uclahs-cds/pipeline-Nextflow-config/releases) - [Commits](uclahs-cds/pipeline-Nextflow-config@da8e990...3ec7186) --- updated-dependencies: - dependency-name: external/pipeline-Nextflow-config dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/submodules/external/pipeline-Nextflow-config-3ec7186
branch
from
9d91432
to
a6eb4bc
Compare
|
@aholmes @nwiltsie Is this something that shouldn't happen and can be fixed. Or should I just add the situation to the instructions at Dependabot Pull Request Protocol |
|
@sorelfitzgibbon In the best case, this came up because In the worst case this came up because a PlantUML image existed, period, and so will come up again any time we rebase a dependabot PR. I'm not sure which of those this is yet, but I've opened uclahs-cds/tool-PlantUML-action#3 to track it. In the meantime |
dependabot
bot
deleted the
dependabot/submodules/external/pipeline-Nextflow-config-3ec7186
branch
|
More info on the PlantUML failure. |
Bumps external/pipeline-Nextflow-config from
da8e990to3ec7186.Commits
3ec7186Merge pull request #60 from uclahs-cds/yashpatel-use-params-resource-allocations8a1c1b3Update CHANGELOG81c96ecUpdate resource allocation function to check and use params setting if availableDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)