# I want to implement my own plugin, what should i look out for?

**URL:** <https://forum.gitea.com/t/i-want-to-implement-my-own-plugin-what-should-i-look-out-for/8974>\
**Category:** General\
**Created:** [April 13, 2024, 3:16pm UTC](https://forum.gitea.com/t/i-want-to-implement-my-own-plugin-what-should-i-look-out-for/8974 "2024-04-13T15:16:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ouvaa](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/ouvaa/32/4609_2.png) [@ouvaa](https://forum.gitea.com/u/ouvaa)\
**Post date:** [April 13, 2024, 3:16pm UTC](https://forum.gitea.com/t/i-want-to-implement-my-own-plugin-what-should-i-look-out-for/8974/1 "2024-04-13T15:16:32Z")

</div>

if i would like to customize and extend gitea, how can i do it without affecting gitea upgrades and being compatible with gitea in future?

---

<div class="post-metadata">

**Author:** ![bootsguider](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/bootsguider/32/6145_2.png) [@bootsguider](https://forum.gitea.com/u/bootsguider)\
**Post date:** [August 1, 2024, 6:13pm UTC](https://forum.gitea.com/t/i-want-to-implement-my-own-plugin-what-should-i-look-out-for/8974/2 "2024-08-01T18:13:15Z")

</div>

To customize and extend Gitea without affecting upgrades and ensuring future compatibility, consider using the following approach:

1. Use Tools and Scripts: Develop external tools or scripts that interact with Gitea’s API instead of modifying the core code.
2. Create Plugins: Check if Gitea supports plugins or extensions, allowing custom features without altering the core.
3. Submit Contributions: Contribute your custom features to the Gitea project, potentially integrating them into the main codebase.
4. Fork Gitea: If extensive customization is necessary, fork the Gitea repository and maintain your version, but keep it updated with the upstream changes to ensure compatibility.