-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
chore(cicd): setup test pipeline #69
Conversation
88466e7
to
bf6c10f
Compare
// For more information, see https://crawlee.dev/ export function getPageHtml(page: Page) { if (process.env.NO_CRAWL !== "true") {
}); // Add first URL to the queue and start the crawl. const jsonFiles = await glob("storage/datasets/default/*.json", { const results = []; await writeFile(config.outputFileName, JSON.stringify(results, null, 2)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.github/workflows/pr.yml
d484b65
to
c6a93cf
Compare
🎉 This PR is included in version 1.2.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
…line chore(cicd): setup test pipeline
The goal of this PR is to setup an automated test pipeline for PRs to make sure that nothing breaks with upcoming changes and safeguard this project's quality.
This PR includes the starting point to run automated tests against all APIs (cli, config file and docker images) to guarantee that the program builds and executes correctly with each upcoming change.
It also adds a workflow to validate (uses amann/action-semantic-pull-request) the title of PRs to make sure that versioning is kept consistent. This is a follow up from:
Related to: