feat(builder): Updated min_value and required docs

[AndreasBackx]

Fixes #3259.

[AndreasBackx]

I'm unsure if force pushed amends or new commits are preferred based on the contributing guidelines as the commits needs to stay atomic and I'm unsure if you will squash or not. Let me know what you prefer, I've been working less on GitHub and more on Phabricator with stacked diffs where this isn't an issue. 😅

Let me know what you think of the changes.

[epage]

I'm unsure if force pushed amends or new commits are preferred based on the contributing guidelines as the commits needs to stay atomic and I'm unsure if you will squash or not.

Go ahead an force-push

Really wish a tool would support squashing fixup commits so people could just push those for easier reviewing.

Let me know what you prefer, I've been working less on GitHub and more on Phabricator with stacked diffs where this isn't an issue. 😅

Huh, for some reason I thought you guys had moved off Phabricator. Maybe its just different parts? Has the effort to keep it going after the company shut down worked out? At my last place, I saw the writing on the wall before the shutdown and was starting to organize the transition off.

[AndreasBackx]

Really wish a tool would support squashing fixup commits so people could just push those for easier reviewing.

I thought that if you squashed on GitHub, you can pick the new message thus I could push fixup commits?

Huh, for some reason I thought you guys had moved off Phabricator. Maybe its just different parts? Has the effort to keep it going after the company shut down worked out? At my last place, I saw the writing on the wall before the shutdown and was starting to organize the transition off.

It was forked a long time ago from what I understand. I think Phabricator works out great internally, I would definitely say it's a better way of working than GitHub/GitLab's pull/merge requests.

[epage]

I thought that if you squashed on GitHub, you can pick the new message thus I could push fixup commits?

Squashing is brute force; you squash down to one commit when there are valid reasons to preserve multiple commits in a PR.

It was forked a long time ago from what I understand. I think Phabricator works out great internally, I would definitely say it's a better way of working than GitHub/GitLab's pull/merge requests.

I'll assume this is because of local modifications :)

btw I made git stack to get some of the benefits of arc while improving on it in other ways (e.g. better rebasing to preserve the tree of commits/branches).