Skip to content

refactor(script): extract parser function in its own file for testing #12

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

Merged
merged 4 commits into from
Jul 8, 2021

Conversation

oscard0m
Copy link
Owner

@oscard0m oscard0m commented Jul 8, 2021

📝 Summary

  • Extract function to parse and change the yaml files into its own file for testing purposes
  • Installed uvu for testing
  • Added basic test suites to assure the parse function:
    • It modifies the file when there's setup-node step without cache option
    • It bumps to setup-node to v2 if it is not already bumped
    • It does not modify the file if no step contains setup-node
    • It does not modify the file if setup-node has cache option already

⛱ Motivation and Context

To control all the possible use-cases before running the script to a GitHub Organization

@oscard0m oscard0m changed the title ref(script): extract parser in its own file for testing refactor(script): extract parser function in its own file for testing Jul 8, 2021
@oscard0m oscard0m merged commit bb97fdb into main Jul 8, 2021
@oscard0m oscard0m deleted the extract-parser-in-its-own-file-for-testing branch July 8, 2021 19:59
@github-actions
Copy link

🎉 This PR is included in version 1.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant