Hyperapp: commit workflow

Created on 26 Apr 2017  路  5Comments  路  Source: jorgebucaran/hyperapp

hey @jbucaran

i'm watching hyperapp, but the very frequent force-push commits really pollute my feed and i am sure other watchers' feeds. it also doesnt help that each commit is the same generic commit message, so is not even interesting.

perhaps it makes sense to create a separate repo or delay pushing the commits until they are in a more-or-less final form? or maybe something else?

Discussion

Most helpful comment

@jbucaran You could just work on hyperapp the same way any other contributor does, by having a fork. This will also help you see issues that other contributors have because you'd do it the same way.

This would also allow people to subscribe to your changes by watching your "private" fork.

All 5 comments

capture2
capture

@leeoniya This sucks. You pointed out "force-push", but is that relevant to the issue? I imagine it will show on your feed regardless of the type of commit it is.

Seems like GitHub could be more useful by collecting the commits under a collapsible list item.

Well, I wasn't really aware that this is how it looks as I don't watch many repos.

perhaps it makes sense to create a separate repo or delay pushing the commits until they are in a more-or-less final form? or maybe something else?

I'll try to do this.

@jbucaran You could just work on hyperapp the same way any other contributor does, by having a fork. This will also help you see issues that other contributors have because you'd do it the same way.

This would also allow people to subscribe to your changes by watching your "private" fork.

yeah, that seems like the way to go

@dodekeract Never occurred to me to do that. Great idea! 馃憤

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Mytrill picture Mytrill  路  4Comments

jacobtipp picture jacobtipp  路  3Comments

zhaotoday picture zhaotoday  路  3Comments

jamen picture jamen  路  4Comments

SkaterDad picture SkaterDad  路  3Comments