Hi!
Following @glennj and @IsaacG guidelines I just finished a new exercise for this track. I already test it in my machine and (at least to me) it’s all fine. And now I’m here to discuss the “issue” with you guys before create any PR (my shame, I’m not familiarized with PR’s …).
My repo: sqlite/exercises/practice/resistor-color-trio at main · jimmytty/sqlite · GitHub
The dificulty is 1 and I don’t know how to define this properly.
Looks good 
Generally, you should ask if maintainers are open to you doing work before you do the work. But we’re open to adding new exercises here!
I’m not sure it makes sense to have a column for a fourth column here, though. Those tests can be skipped.
Sorry for not asking before, I preferred to do the work and ask later if anyone was interested in it. I wasn’t completely sure I could do the job and in a timely manner.
About the fourth column, I just kept it consistent with canonical-data.json, the last case is “Ignore extra colors”. But I can change this if you like.
As per above, my vote is to drop it and skip the test. It doesn’t make sense in the context of SQL.
I removed the fourth column and the last test (about “ignoring more than 3 colors”). I’ve already tested the exercise again and it’s all in my repository now.
Can I make a Pull Request? If yes, I should use this documentation Creating a pull request from a fork?
Yes and yes. The maintainers might have other feedback on the PR and ask you to change other things, as is part of the PR process ;) But feel free to create a PR!
PR created.
Exercises can have a difficulty between 1 and 10. The website uses that difficulty to label an exercise as easy (1-3), medium (4-6), or hard (7-10). Students get slightly more reputation for publishing a solution depending on that label. Tracks often also sort their exercises by difficulty so the easier exercises are at the top of the list and easier to find.
Choosing a particular difficulty is a bit more of an art than a science. Exercises are set often even within a track by different people at different times. On a track new to me, I try and solve a couple of existing exercises at easy and medium difficulty levels. I can then use that experience as a reference.
However, the maintainers might also suggest a difficulty during the code review. That makes it easier. 