# Comment pourrait-on implémenter un workflow CI pour les plugins non officiels ?

**URL:** https://meta.discourse.org/t/how-could-a-ci-workflow-for-unofficial-plugins-be-implemented/271774
**Category:** Development
**Created:** [Juillet 16, 2023, 8:02 UTC](https://meta.discourse.org/t/how-could-a-ci-workflow-for-unofficial-plugins-be-implemented/271774 "2023-07-16T08:02:44Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [Juillet 16, 2023, 8:22 UTC](https://meta.discourse.org/t/how-could-a-ci-workflow-for-unofficial-plugins-be-implemented/271774/2 "2023-07-16T08:22:47Z")

</div>

Ceci pourrait être utile :

> [@Setup Continuous Integration using GitHub Actions](https://meta.discourse.org/t/setup-continuous-integration-using-github-actions/240150):
>
> mag Overview To build a robust extension for Discourse, it can be wise to include Continuous Integration (CI) into your plugin or theme-component. This will help to detect errors early on and lessen the chances of bugs in your code. Setting up a CI workflow using [GitHub Actions](https://github.com/features/actions) to automate builds and testing is an approach the Discourse team uses on all our components, and we recommend you do the same. gear Setting it up To add automated workflows for GitHub actions to detect, you need to …

---

_[View the full topic](https://meta.discourse.org/t/how-could-a-ci-workflow-for-unofficial-plugins-be-implemented/271774)._