# Is there a method to create meaningful commit labels or to reset my progress to a specific stage?

**URL:** <https://forum.codecrafters.io/t/is-there-a-method-to-create-meaningful-commit-labels-or-to-reset-my-progress-to-a-specific-stage/7230>\
**Category:** Platform\
**Created:** [March 20, 2025, 7:37pm UTC](https://forum.codecrafters.io/t/is-there-a-method-to-create-meaningful-commit-labels-or-to-reset-my-progress-to-a-specific-stage/7230 "2025-03-20T19:37:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sundmoon](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.codecrafters.io/sundmoon/32/3132_2.png) [@sundmoon](https://forum.codecrafters.io/u/sundmoon)\
**Post date:** [March 20, 2025, 7:37pm UTC](https://forum.codecrafters.io/t/is-there-a-method-to-create-meaningful-commit-labels-or-to-reset-my-progress-to-a-specific-stage/7230/1 "2025-03-20T19:37:21Z")

</div>

The local Git history seems to be the platform implementation, and it is not helpful to me as an artifact.

Is there any way to reset the project progress to a specific stage on the platform side?

Alternatively, please document an approach to create a branching and tagging system on the client side. The drawback is that it must be followed strictly from the beginning.

As a newcomer, lost in refactorings, I am tempted to delete my account and start from scratch. If I make significant investments, that won’t be an option.

---

<div class="post-metadata">

**Author:** ![andy1li](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.codecrafters.io/andy1li/32/10_2.png) [@andy1li](https://forum.codecrafters.io/u/andy1li)\
**Post date:** [March 24, 2025, 12:28pm UTC](https://forum.codecrafters.io/t/is-there-a-method-to-create-meaningful-commit-labels-or-to-reset-my-progress-to-a-specific-stage/7230/5 "2025-03-24T12:28:56Z")

</div>

> Is there any way to reset the project progress to a specific stage on the platform side?

Hey @sundmoon, we don’t currently support resetting progress to a specific stage. However, you can **restart a challenge** if you want a fresh start:

 ![image](https://canada1.discourse-cdn.com/flex003/uploads/codecrafters/original/2X/3/3c21f839e97629e81bc4e9af1093e2f5f8bc981e.png)

> Alternatively, please document an approach to create a branching and tagging system on the client side.

Could you clarify what you have in mind for that? We only track commits on the **master** branch, so you’re free to use any branching or tagging strategy you want.

> The drawback is that it must be followed strictly from the beginning.

The commit messages can be whatever you prefer. Could you share more about what’s giving you trouble?