The default settings only show commits pushed to master. The /github subscribe owner/repo commits:all will show all commits pushed to any branch. I could imagine a scenario where a team might want to see any commits that were _force-pushed_ to any branch.
We should consider adding something like commits:forced
cc #255
It may be a better idea for it to be configured in such a way to only show force-pushes on certain branches, not all. In my org, people are rebasing and force-pushing to their branches all the time and that would only create noise.
We like to see only non-force-push commits on other people's branches since we're relatively small, so I imagine the following may be an all-inclusive configuration:
commits -> commits on default branch
commits:all -> commits on all branches (**excludes force-pushes--the current version shows force-pushes**)
commits:<branch> -> commits on certain branches, there can be multiple of these or comma-separated?
commits:forced -> force-pushes on default branch
commits:forced:all -> force-pushes on all branches
commits:forced:<branch> -> force-pushes on certain branches, there can be multiple of these or comma-separated?
:<branch> ones are not necessarily useful in the use-case I described, but I imagine others would find it useful.
Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed.
@stale Still relevant.
Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed.
@Stale Still relevant.
Most helpful comment
It may be a better idea for it to be configured in such a way to only show force-pushes on certain branches, not all. In my org, people are rebasing and force-pushing to their branches all the time and that would only create noise.
We like to see only non-force-push commits on other people's branches since we're relatively small, so I imagine the following may be an all-inclusive configuration:
:<branch>ones are not necessarily useful in the use-case I described, but I imagine others would find it useful.