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
Merging tags to most common spellings #637
Comments
@maxpou go for it There was an issue kicking around to deduplicate tags in the code but the agreed upon approach is to edit the data file. Ideally, make 1 PR per tag that you're unifying. |
@HugoDF there you go. As said before, I arbitrary took the most popular keyword
Someone can confirm this?
|
This is correct, in this case I would use "Ruby on Rails" |
fix(data): merge frontend tag (#637)
We could list these common spellings at the top of |
Hi, I've been cleaning up some tags and realised that since it's actually really easy that this issue should perhaps be labelled "good for first-time" or similar. Would a maintainer be so kind as to do this if they agree? |
Merge duplicate Tailwind CSS tags (Issue #637)
Merge duplicate Full Stack tags (Issue #637)
I'm planning on merging the VSCode tags next. Which spelling is preferable: Visual Studio Code, VS Code or VSCode ? |
Merge duplicate DevOps tags(Issue #637)
Merge duplicate Open Source Software tags (Issue #637)
Merge duplicate JAMstack tags (Issue #637)
Merge duplicate Front End tags (Issue #637)
Merge duplicate Node.js tags (Issue #637)
fix(data) merge express tag (#637)
fix(data): merge vscode tag (#637)
I can see that this issue has a long history and @BlakeCampbells looks to have made progress in merging tags. Is this issue now completed, or is there work still to do? |
Good call @carbontwelve , I think this is okay to close. To keep it from happening in the future we should add either some validation around tags or in |
hiya,
I just noticed that same filters have been repeated twice or more.
We have:
Do you mind if I merge people's tags to the most used?
The text was updated successfully, but these errors were encountered: