You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discovered an interesting bug/consequence-of-the-data-model today. Say you have a saved search for 'repos: foo' (implicitly this only covers the master branch). Then you make commit c1 to the branch B. When barkeep picks up this commit, it checks to see who has a saved search that includes c1 (probably nobody, unless someone is watching branch B or 'branches: all'). Then if you later merge c1 to master, it's not a new commit and so no email is ever sent.
The text was updated successfully, but these errors were encountered:
Discovered an interesting bug/consequence-of-the-data-model today. Say you have a saved search for 'repos: foo' (implicitly this only covers the master branch). Then you make commit c1 to the branch B. When barkeep picks up this commit, it checks to see who has a saved search that includes c1 (probably nobody, unless someone is watching branch B or 'branches: all'). Then if you later merge c1 to master, it's not a new commit and so no email is ever sent.
The text was updated successfully, but these errors were encountered: