the contributor will not be visible in the list (as any balance will be 0).
What other feedback can we give the user to indicate that the contributor was added?
the contributor will not be visible in the list (as any balance will be 0).
What other feedback can we give the user to indicate that the contributor was added?
raucao
(Migrated from github.com)
reviewed 2018-04-07 12:44:33 +00:00
Sorry, that's from preventing force-pushes. Please just don't force-push in the future, when it's a branch of an open pull request, and it is not an emergency change. You, or the person merging, can squash or rebase the history before it lands in master. It's easy to just close a PR and ref it from a new one, with the changed history. Thanks.
Sorry, that's from preventing force-pushes. Please just don't force-push in the future, when it's a branch of an open pull request, and it is not an emergency change. You, or the person merging, can squash or rebase the history before it lands in `master`. It's easy to just close a PR and ref it from a new one, with the changed history. Thanks.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
the contributor will not be visible in the list (as any balance will be 0).
What other feedback can we give the user to indicate that the contributor was added?
Just a
window.alert()would do for starters.Done.
@skddc can you delete the branch? It says it is locked: https://github.com/67P/kredits-web/branches
Sorry, that's from preventing force-pushes. Please just don't force-push in the future, when it's a branch of an open pull request, and it is not an emergency change. You, or the person merging, can squash or rebase the history before it lands in
master. It's easy to just close a PR and ref it from a new one, with the changed history. Thanks.