Need your feedback for research on evaluating automated conversion from GitHub Actions workflows to Travis CI#583
Closed
nhossaincse wants to merge 1 commit intoSAP-samples:mainfrom
Closed
Need your feedback for research on evaluating automated conversion from GitHub Actions workflows to Travis CI#583nhossaincse wants to merge 1 commit intoSAP-samples:mainfrom
nhossaincse wants to merge 1 commit intoSAP-samples:mainfrom
Conversation
|
|
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 Travis CI configuration reflects your original GitHub Actions workflow 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! |
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.
I am doing research on evaluating automated conversion of CI configurations from GitHub Actions to Travis CI. As part of this study, a Travis CI configuration has been generated that aims to approximate the existing GitHub Actions workflow as closely as possible.
Even if you do not have plans to actually migrate to Travis CI, I would greatly appreciate it if you could give me some feedback on how well this migrated configuration reflects the original GitHub Actions workflow. You may also give me your opinion in a five-point rating; it would be very helpful for the study. I just added the .travis.yml file, and it has passed (green) on my end. Thank you.