# \#github

**URL:** https://forums.maslowcnc.com/tag/github/10.md

[Latest](https://forums.maslowcnc.com/latest.md) · [Categories](https://forums.maslowcnc.com/categories.md) · [Tags](https://forums.maslowcnc.com/tags.md)

---

## [Index.html.gz source](https://forums.maslowcnc.com/t/index-html-gz-source/21187)

<div class="topic-metadata">

**Author:** [@iliaden](https://forums.maslowcnc.com/u/iliaden)\
**Replies:** 9\
**Last updated:** [May 23, 2024, 8:20pm UTC](https://forums.maslowcnc.com/t/index-html-gz-source/21187 "2024-05-23T20:20:04Z")

</div>

So I finally started looking at the source code of the webUI with the goal of implementing some of the quality of life features ( adding a bounding box / printing the max X and Y dimensions of the gcode, adding a command…

---

## [Top Beam Tilt Correction Pull-Request](https://forums.maslowcnc.com/t/top-beam-tilt-correction-pull-request/7307)

<div class="topic-metadata">

**Author:** [@johnboiles](https://forums.maslowcnc.com/u/johnboiles)\
**Replies:** 35\
**Last updated:** [June 25, 2019, 3:35am UTC](https://forums.maslowcnc.com/t/top-beam-tilt-correction-pull-request/7307 "2019-06-25T03:35:14Z")

</div>

The purpose of this thread is to discuss the merits and drawbacks of adding top-beam-tilt correction into the Maslow firmware and GroundControl. At @bar’s request we are moving discussion here (instead of GitHub) so that…

---

## [What's the correct way to update from github?](https://forums.maslowcnc.com/t/whats-the-correct-way-to-update-from-github/1342)

<div class="topic-metadata">

**Author:** [@vertex](https://forums.maslowcnc.com/u/vertex)\
**Replies:** 8\
**Last updated:** [December 5, 2017, 8:43pm UTC](https://forums.maslowcnc.com/t/whats-the-correct-way-to-update-from-github/1342 "2017-12-05T20:43:31Z")

</div>

I installed from github: see topic now i’m trying to figure out the correct way to keep this up to date. And eventually an option to roll back if an update breaks things… as this uses the development version… So i ki…