# Cleaning up our GitHub issue labels

**URL:** <https://forum.openrefine.org/t/cleaning-up-our-github-issue-labels/755>\
**Category:** Development & Design\
**Created:** [May 9, 2023, 11:45am UTC](https://forum.openrefine.org/t/cleaning-up-our-github-issue-labels/755 "2023-05-09T11:45:14Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![lozanaross](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/lozanaross/32/33_2.png) [@lozanaross](https://forum.openrefine.org/u/lozanaross)\
**Post date:** [August 20, 2023, 1:24pm UTC](https://forum.openrefine.org/t/cleaning-up-our-github-issue-labels/755/27 "2023-08-20T13:24:10Z")

</div>

Hi @tfmorris & @antonin_d - I think the outstanding questions here seem to be more or less answered, or? [Organizing Github Issues - Google Docs](https://docs.google.com/document/d/19LLxQxQNgELxSuxT8nwgoWEHMdlGjjnJO20zFsZpLak/edit?usp=sharing)

In general, we can remove all duplicates (or labels that duplicate build-in functionalities in Github), but the rest can maybe already be implemented, so we can start using them in the documentation?

What do you think? Is there any benefit in waiting a bit longer, or shall we give the new structure a try and see if we hit any snags with it.

---

_[View the full topic](https://forum.openrefine.org/t/cleaning-up-our-github-issue-labels/755)._