Improving CORE support?

39 views
Skip to first unread message

Jonathan Savage

unread,
Jun 29, 2025, 4:24:32 AM6/29/25
to golden-cheetah-developers
GC has support for displaying core temperature from the CORE sensor. However, I find that of far less value than the Heat Strain Index. 

I forked GC and added support for displaying HSI and skin temperature, both as numeric displays and graph lines. 

Is this something I should look to contribute to the main code base? (I've never contributed to GC or any other public github, though I was a software engineer for decades.) 

Jonathan 

Ale Martinez

unread,
Jun 29, 2025, 4:24:39 PM6/29/25
to golden-cheetah-developers
Hi Jonathan, welcome to the project, there is a document in the wiki which may help: https://github.com/GoldenCheetah/GoldenCheetah/wiki/Guidelines-for-submitting-a-patch 

Cheers, Ale.

Jonathan Savage

unread,
Jul 11, 2025, 9:34:00 AM7/11/25
to golden-cheetah-developers
I've uploaded a patch file to the issue I created. Let me know what else I need to do, or if I took the wrong approach. 


Thanks, Jonathan 

Ale Martinez

unread,
Jul 11, 2025, 7:20:10 PM7/11/25
to golden-cheetah-developers
El viernes, 11 de julio de 2025 a la(s) 10:34:00 a.m. UTC-3, Jonathan Savage escribió:
I've uploaded a patch file to the issue I created. Let me know what else I need to do, or if I took the wrong approach. 

Hi Jonathan for small modifications patch files are Ok, otherwise GitHub pull request are much better since you have automatic ci builds and they are easier for maintainers to review, see https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

Thanks, Ale. 

Jonathan Savage

unread,
Jul 12, 2025, 5:56:18 AM7/12/25
to golden-cheetah-developers
I'm not sure how to proceed. I don't have write permission to create a branch in the main GC repo, but I already have a fork of GC that has my personal changes that I don't intend to feed back. It looks like I'd have to create a second account, use that to fork GC, apply the patch of my changes to the second fork, then create a pull request from there. 

Am I missing something? 

Jonathan 

Poncho

unread,
Jul 12, 2025, 6:19:39 AM7/12/25
to golden-cheet...@googlegroups.com
You can create a branch in your fork. That branch needs to be in line
with the upstream master branch.
Then you can add the commits that you want to contribute
(cherry-picking) to that branch and open a pull request.

You don't need a second account or a second fork.

It's git. It's a bit hard to explain. If you get the hang of it, it will
make sense eventually 🤷‍♂️

Jonathan Savage

unread,
Jul 12, 2025, 7:09:04 AM7/12/25
to golden-cheetah-developers
Thanks! It was a bit confusing, especially being able to create a branch in a fork that's based on a later branch of the main fork. But I think it worked, and it looks like there's a new pull request in the main GC fork. 

Let me know if this looks okay, or if I got something wrong. 

Jonathan 

Ale Martinez

unread,
Jul 12, 2025, 8:29:27 AM7/12/25
to golden-cheetah-developers
Yes, it looks ok, thank you!
Reply all
Reply to author
Forward
0 new messages