# Automating +1 data points for updated GitHub issues

**URL:** <https://forum.beeminder.com/t/automating-1-data-points-for-updated-github-issues/12414>\
**Category:** Tech\
**Created:** [June 10, 2025, 12:53pm UTC](https://forum.beeminder.com/t/automating-1-data-points-for-updated-github-issues/12414 "2025-06-10T12:53:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![aad](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/aad/32/4736_2.png) [@aad](https://forum.beeminder.com/u/aad)\
**Post date:** [June 10, 2025, 12:53pm UTC](https://forum.beeminder.com/t/automating-1-data-points-for-updated-github-issues/12414/1 "2025-06-10T12:53:34Z")

</div>

I wanted to play with val.town and Beeminder provided the case 🤓

[Take a look!](https://www.val.town/x/cricks_unmixed4u/gissue-rolodex) Give it a try!

For now it’ll just get all issues of a repository. So if you e.g. have a repository that should feed into two goals, that’ll be tricky.

val.town has some social features, so you can “remix” (similar to forking on GitHub) your own solution for that, if that’s useful for you 🙂

(I’m pretty impressed by [val.town](https://docs.val.town/), without any affiliation 😉 I think it already has become the go-to tool for deploying JavaScript code for me.)

---

<div class="post-metadata">

**Author:** ![bee](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/bee/32/41_2.png) [@bee](https://forum.beeminder.com/u/bee)\
**Post date:** [June 11, 2025, 11:53pm UTC](https://forum.beeminder.com/t/automating-1-data-points-for-updated-github-issues/12414/2 "2025-06-11T23:53:38Z")

</div>

did you know the [github integration](https://www.beeminder.com/gitminder) tracks issues? i guess it doesn’t get all issues, only the ones that are assigned to you. And maybe it only counts them once they’re closed, and not updated? i don’t think our github minding is very robust to different ways of using gissues, now that i’m saying this out loud…

---

<div class="post-metadata">

**Author:** ![aad](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/aad/32/4736_2.png) [@aad](https://forum.beeminder.com/u/aad)\
**Post date:** [June 12, 2025, 9:16am UTC](https://forum.beeminder.com/t/automating-1-data-points-for-updated-github-issues/12414/3 "2025-06-12T09:16:26Z")

</div>

Yeah, this gave me the impression it wouldn’t work with updates on issues 🙂

 ![image](https://us1.discourse-cdn.com/flex019/uploads/beeminder/original/2X/5/56b20dec65a220b36be84fdd6173bc8108adf9aa.png)

---

<div class="post-metadata">

**Author:** ![aad](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/aad/32/4736_2.png) [@aad](https://forum.beeminder.com/u/aad)\
**Post date:** [July 1, 2025, 6:06pm UTC](https://forum.beeminder.com/t/automating-1-data-points-for-updated-github-issues/12414/4 "2025-07-01T18:06:38Z")

</div>

Now updated (v61 [val](https://www.val.town/x/cricks_unmixed4u/gissue-rolodex/branch/main/code), [source](https://esm.town/v/cricks_unmixed4u/gissue-rolodex@61-main/main.cron.tsx)) to update the goal for an issue once per day.