Skip to content
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

🔄 synced file(s) with neurobagel/workflows #151

Merged
merged 1 commit into from
Jan 7, 2025

Conversation

neurobagel-bot[bot]
Copy link
Contributor

@neurobagel-bot neurobagel-bot bot commented Jan 7, 2025

synced local file(s) with neurobagel/workflows.

Changed files
  • synced local .github/workflows/build_docker_nightly.yml with remote template_workflows/build_docker_nightly.yml

This PR was created automatically by the repo-file-sync-action workflow run #12644813733

Summary by Sourcery

CI:

  • Update the build docker nightly workflow to include a note about a custom version used in neurobagel/query-tool.

…te 'template_workflows/build_docker_nightly.yml'
@neurobagel-bot neurobagel-bot bot added the _bot [BOT only] Issue or PR made by a bot. label Jan 7, 2025
Copy link

sourcery-ai bot commented Jan 7, 2025

Reviewer's Guide by Sourcery

This PR synchronizes the .github/workflows/build_docker_nightly.yml workflow file with the template from the neurobagel/workflows repository. A comment was added to the top of the file to indicate that a custom version of this file is used in neurobagel/query-tool and that changes must be applied manually.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Added a comment to the top of the build_docker_nightly.yml file.
  • Added a comment indicating that a custom version of the workflow is used in neurobagel/query-tool.
  • Added a comment explaining that changes to the template must be manually applied to the neurobagel/query-tool version of the file.
.github/workflows/build_docker_nightly.yml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time. You can also use
    this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

codecov bot commented Jan 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.17%. Comparing base (14e1b39) to head (1ff7a4e).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #151   +/-   ##
=======================================
  Coverage   97.17%   97.17%           
=======================================
  Files          23       23           
  Lines         707      707           
=======================================
  Hits          687      687           
  Misses         20       20           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@alyssadai alyssadai merged commit 227ee60 into main Jan 7, 2025
11 checks passed
@alyssadai alyssadai deleted the repo-sync/workflows/default branch January 7, 2025 04:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
_bot [BOT only] Issue or PR made by a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant