Sorry for the churn, @ErikSchierboom and/or @glennj
Could you add me as a maintainer? Maybe it’s time I actually get involved in the core building part of launching a track.
GH Handle: IsaacG
1 Like
Absolutely. You’ve been added.
1 Like
@ErikSchierboom Could we get GDScript launched?
@pfertyk @codingthat @Meatball @zeektvbox01-hub Could you kindly confirm that you would still like to be involved in maintaining this track and/or would like to be removed? If there’s no response in a week, I’m going to assume you’re no longer active and ask that you be removed. We’d be happy to have you rejoin but it’s helpful to have only active members on the list so we’re not blocked on inactive people.
1 Like
Is the test runner working? If so, just submit and merge a PR to the track repo where active is set to true. That’s all
Yes, the test runner is working. I wanted to open this up for maintainer testing … but it looks like that’s already done! Thanks.
A long and winding road for this track: the test runner was activated 2.5 years ago
4 Likes
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