Skip to content

fix: migrator syntax problem #4031

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

Open
wants to merge 10 commits into
base: main
Choose a base branch
from
Open

Conversation

germa89
Copy link
Collaborator

@germa89 germa89 commented Jun 23, 2025

Description

Fix markdown code outside js literal string. Also small improvements.

More improvements fix should arise with usage.

Issue linked

Checklist

Summary by Sourcery

Fix syntax issues and enhance robustness in the migrator GitHub Actions workflow

Bug Fixes:

  • Fix quoting of the github-token input and correct variable references (e.g., comment_id)
  • Correct destructuring of pull request data from the GitHub API

Enhancements:

  • Add fallback git fetch-and-push logic for failed pushes
  • Switch from octokit to the github client for assigning PR assignees
  • Tidy PR body string formatting in the workflow script
  • Introduce comment_id environment variable for consistency

CI:

  • Prevent failure comment on retry when triggered by workflow_dispatch events

@germa89 germa89 requested a review from a team as a code owner June 23, 2025 09:37
@ansys-reviewer-bot
Copy link
Contributor

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

Copy link
Contributor

sourcery-ai bot commented Jun 23, 2025

Reviewer's Guide

This PR refactors the GitHub Actions migrator workflow to correct JS template syntax, bolster git push reliability, standardize inputs, introduce missing variables, streamline REST API calls, and refine conditional logic for comment creation.

File-Level Changes

Change Details Files
Enhanced git push retry logic
  • Chained git fetch with retry on push failure
  • Retained force-with-lease in all retry attempts
.github/workflows/migrator.yml
Standardized GitHub token input
  • Removed extra quotes around the github-token input
.github/workflows/migrator.yml
Introduced comment_id variable
  • Declared const comment_id from env
  • Replaced direct env reference with the variable
.github/workflows/migrator.yml
Streamlined REST API calls
  • Destructured pulls.get response as data: originalPR
  • Added const for newPrData when creating PR
  • Switched from octokit.request to github.request for assignees
.github/workflows/migrator.yml
Fixed PR body template formatting
  • Adjusted backticks and commas to properly embed markdown
  • Inserted a blank line after the 'Closes' line
.github/workflows/migrator.yml
Refined failure comment condition
  • Added github.event_name != 'workflow_dispatch' to the if clause
  • Maintained single-run failure comment guard
.github/workflows/migrator.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. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the 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 exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

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

@germa89 germa89 self-assigned this Jun 23, 2025
@github-actions github-actions bot added CI/CD Related with CICD, Github Actions, etc maintenance General maintenance of the repo (libraries, cicd, etc) bug Issue, problem or error in PyMAPDL labels Jun 23, 2025
Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @germa89 - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link

codecov bot commented Jun 23, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.12%. Comparing base (27d26c4) to head (0c831b5).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4031      +/-   ##
==========================================
- Coverage   89.17%   89.12%   -0.05%     
==========================================
  Files         187      187              
  Lines       14970    14970              
==========================================
- Hits        13349    13342       -7     
- Misses       1621     1628       +7     
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@germa89 germa89 requested a review from RobPasMue June 23, 2025 11:46
@germa89
Copy link
Collaborator Author

germa89 commented Jun 23, 2025

It seems I did a total mess up in #3973. I am fixing that in here.

@germa89
Copy link
Collaborator Author

germa89 commented Jun 25, 2025

Pinging @RobPasMue @jorgepiloto @MaxJPRey for review/awareness.

Copy link
Member

@RobPasMue RobPasMue left a comment

Choose a reason for hiding this comment

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

Small comments, LGTM!

You can clone this branch in a new repository by doing:
~~~terminal
git clone -b ${prHeadBranch} --single-branch https://github.com/ansys/pymapdl.git
Copy link
Member

Choose a reason for hiding this comment

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

Can't you programatically get the repository from the PR context? Just wondering

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, I can. I believe github.repository is the way.

If you have [GitHub CLI](https://cli.github.com/) installed, you can also use the following command to check out the pull request:
~~~terminal
gh pr checkout https://github.com/ansys/pymapdl/pull/${prNumber}
Copy link
Member

Choose a reason for hiding this comment

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

Same here

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Sure!

I guess want me to prepare the workflow to be less PyMAPDL-dependent, for the future migration to ansys/actions if that ever happens.

Copy link
Member

Choose a reason for hiding this comment

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

You got my point without even saying it 😄

Copy link
Collaborator Author

@germa89 germa89 Jun 25, 2025

Choose a reason for hiding this comment

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

Very well then. I will reping you when ready :)

Copy link
Member

Choose a reason for hiding this comment

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

Thanks @germa89 - much appreciated. Getting this as agnostic as possible from the repo will allow you to migrate it seamlessly. This is honestly a great feature.

Copy link
Contributor

Choose a reason for hiding this comment

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

Good approach. It will be helpful for all of us. Thanks @germa89

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue, problem or error in PyMAPDL CI/CD Related with CICD, Github Actions, etc maintenance General maintenance of the repo (libraries, cicd, etc)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants