mirror of
https://github.com/lipis/flag-icons.git
synced 2026-04-26 09:25:50 +03:00
[GH-ISSUE #1383] CONTRIBUTING.md #617
Labels
No labels
3rd-party
3rd-party
bug
code
documentation
enhancement
fixed-in-master
flag-request
help needed
missing-flag
missing-flag
pull-request
wrong-flag
wrong-flag
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/flag-icons#617
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @p2made on GitHub (Jun 18, 2025).
Original GitHub issue: https://github.com/lipis/flag-icons/issues/1383
This replaces #1364, because I learned that I was effectively proposing a CONTRIBUTING.md file. This would help any who want to contribute know what is expected; what standards are required, what we should or should not do, & what flags may or may not be included. I hope that documenting expectations & requirements would make it easier for @lipis through, as examples, some being able to submit a quality PR instead of posting an issue, & some may be able to [say] see a flag request, attend to it, & submit a quality PR.
On what flags may or may not be included, I hope that many flags may be included, & few may not. I've said elsewhere that I'm big on representation, and flags are a means of representation. With that in mind...
Originally posted by @lipis in #1183
And yes‼️ I hope we can include them all 🙃 I hope the scope of what flags can be included can be broad enough to allow for a wealth of representation.
The flags of interest to me for my own work are probably a couple of dozen. Adding logical extensions to those (completing the Federal subjects of Russia & Oblasts of Ukraine), & a couple of side quests, and I have well over 100 that I could contribute. I've actually done most of them, & I maintain an extension to
flag-iconsthat makes them available to my work, but that doesn't make them available to others. Adding them toflag-iconswould. I also have many of these is a few branches ready to submit as PRs.Other considerations...
Optimisation: SVGs in
flag-icinsare optimised usingsvgowhich makes a whole lot of sense. I've developed my own scripted workflow for that. Having the correct use documented would ensure consistency & should make less work for @lipis.Size: I've concluded from looking at existing SVGs that it's 640x480 & 512x512 (I think I've seen a couple of exceptions). Having it explicitly specified would be helpful.
Curation: How should flags submitted in PRs be curated? Logical groupings or collections makes sense to me, although one person's idea of what makes a logical grouping might differ from another's. Also, some logical groupings might be large. There are 83 Federal subjects of Russia & almost 30 Oblasts of Ukraine.
Other work: Should someone submitting flags in a PR also update
country.json&_variables.scss(was_flag-icons-list.scss) and recompile the CSS?There's are probably more that I haven't thought of. I offer these thoughts in the spirit of wanting to be helpful to all.
@p2made commented on GitHub (Jun 18, 2025):
My own contributions, & potential contributions, are...
.DS_Storefiles intoflag-icons.@NotTsunami commented on GitHub (Sep 23, 2025):
https://github.com/lipis/flag-icons/pull/848/files
I did go to add this at one point, feel free to cherry-pick and modify if you'd like