Skip to content
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

More documentation for setting up Continuous Integration #338

Open
dfabulich opened this issue Feb 16, 2025 · 0 comments
Open

More documentation for setting up Continuous Integration #338

dfabulich opened this issue Feb 16, 2025 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@dfabulich
Copy link

https://skip.tools/docs/faq/#ci

Can Skip frameworks be built and tested using continuous integration systems?
Skip framework projects contain built-in support for running parity tests for both the Swift and Kotlin sides of a project. These tests can be included in automated continuous integration workflows to ensure that the tests are always passing. We do this ourselves for the various Skip frameworks, such as the SkipLib Actions, which references our standard GitHub CI workflow.

The documentation here should at least link to https://github.com/skiptools/actions/ and https://github.com/skiptools/actions/tree/main/.github/workflows

I think I would remove the link to https://github.com/skiptools/skip-lib/actions. That's just a report of Github Action results. (I guess it's just a social proof, "see, wee use it, too" but I don't think the sort of person reading this answer needs that proof.)

It would also be great if skip init were to add example workflows.

@marcprux marcprux added the documentation Improvements or additions to documentation label Feb 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants