Skip to content

Conversation

@nhossaincse
Copy link

I am doing research on evaluating automated conversion of CI configurations from Travis CI to GitHub Actions. As part of this study, a GitHub Actions workflow has been generated that aims to approximate the existing Travis CI configuration as closely as possible.

In this case, the generated workflow did not complete successfully during our test run, but we are still very interested in understanding how well the translated workflow reflects the structure and intent of your original Travis CI setup. Even if you do not have plans to migrate to GitHub Actions, I would greatly appreciate any feedback you can provide on how well this migrated workflow aligns with the original configuration. You may also give a five-point rating, which would be very helpful for the study.I just added the actions.yml file. Thank you.

@nhossaincse
Copy link
Author

Dear Authors,

I wanted to follow up on the PR.

I understand reviewing research PRs may not be a priority, but even brief feedback on how well the converted GitHub Actions workflow captures the original Travis CI configuration would be incredibly helpful for my study. A simple 1-5 rating would be great and highly appreciated.

Thank you!

@nhossaincse
Copy link
Author

Dear Authors,

Apologies for the additional follow up, and wanted to gently check in once more regarding this research PR.

If you have a moment, even brief feedback on whether the generated GitHub Actions workflow reflects your original Travis CI configuration would be extremely valuable for my study. A simple 1 to 5 rating (5 being the best) would be great and highly appreciated.

Thank you!

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.

1 participant