Well. Hopefully we can merge. I noticed parse/compile errors are not surfaced on the UI which is pretty bad. Once that is fixed and some maintainers poke at it, hopefully we can get it launched!
I can take a look later this week / weekend.
Yes,but I will work on the .approaches
1 Like
That sounds good. Though if you’re up for content creation, creating practice exercises and/or concept docs/exercises might be of even higher value!
accidently put a commit on main instead of my branch,how to revert
Very carefully 
git reset HEAD^ to move back to the prior commit, then push.
It’s generally good practice to not use main for work, but use a separate branch.
Could you help me with that
Commit a0622da
Done.
$ git checkout main
Already on 'main'
Your branch is up to date with 'origin/main'.
$ git pull origin main
From github.com:exercism/gdscript
* branch main -> FETCH_HEAD
Already up to date.
$ git log --oneline | head -n3
a0622da GDScript Math concept docs # <== HEAD
aa30bb0 [scrabble-score] Add new practice exercise (#173) # <== HEAD^
c9dc928 [perfect-numbers] Add new practice exercise (#172) # <== HEAD^^
$ git reset HEAD^
$ git status
On branch main
Your branch is behind 'origin/main' by 1 commit, and can be fast-forwarded.
(use "git pull" to update your local branch)
$ git log --oneline | head -n2
aa30bb0 [scrabble-score] Add new practice exercise (#173)
c9dc928 [perfect-numbers] Add new practice exercise (#172)
$ git push origin main
To github.com:exercism/gdscript
! [rejected] main -> main (non-fast-forward)
error: failed to push some refs to 'github.com:exercism/gdscript'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. If you want to integrate the remote changes,
hint: use 'git pull' before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
$ git push --force origin main
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
To github.com:exercism/gdscript
+ a0622da...aa30bb0 main -> main (forced update)
Resetting your local repo can be slightly tricky now as your local main is one commit ahead of origin main.
1 Like
We’re up to 40 exercises (though I’ve definitely been spamming the simpler ones).
If there’s no objections and nothing missing, I’ll mark the track active sometime in the next day or three.
1 Like
Yes,ready!
The track is now live. 
2 Likes
@zeektvbox01-hub Note, now that the track is live, all PRs need a maintainer approval – and not from the author. So I’ll need your review and approval on any PRs 
Could you ask someone else? I do not have much time to do these
Unfortunately, it needs to be the track maintainer. If you can’t review track PRs, you can remove yourself from the track maintainer group. That group controls who must be involved in PRs.
I’ve added myself to the team
1 Like
FYI here’s the maintainer expectations: https://exercism.org/docs/community/maintainers#h-responsibilities. If you want to contribute to the track but don’t want to be a maintainer, that’s perfectly fine, too!
1 Like
Hi everyone, sorry for my late reply here — it’s truly weird, because my forum settings (and this particular thread’s settings) show that I should be notified by email about every reply, which I had been, as of June. I didn’t get (and still haven’t gotten) any notifications about the recent activity here, unfortunately, so I caught on a week late with the flood of GitHub emails, but as that grew, so did the time needed to look at it all, and it happened to be a bit of a crazy two weeks for me.
All that to say, I’m stoked that you all took it across the finish line! Nicely done! I guess I will stay off the maintainer group for now and maybe just help by using the new track and providing feedback when I get a moment.
Anyway, thank you for your work here and for your earlier support and collaboration.
1 Like
We could add you back anytime you’d like if you want to join back in.