Generally, we aim for efficiency, and we value trust over enforcement.
That means we mostly use comments and rarely use the request_changes feature in Github,
unless we've identified things that we think will be blockers in the near future if they don't get fixed now.
We respect each other's input and take it seriously, so even if it's only a comment, we will at least respond to every comment, even if we don't implement the suggestions as written.
Merged from https://github.com/joelparkerhenderson/git_commit_message and https://chris.beams.io/posts/git-commit/
A Webhook, in simple terms, is a user-defined HTTP callback. It is a mechanism for the system to notify you about an event.
In our case, we need to send messages to a particular channel in slack. Slack calls in Incoming Webhook. It is a mechanism
to send messages to your Slack Channel from external sources. These external sources could be any application or service
that is capable of sending a JSON payload over HTTP into a Slack Channel. Each Channel will be identified by a
unique Incoming Webhook URL to which you can post the message from outside. This configuration is done via the Integrations for your channel.
incoming webhook integration below the heading Incoming Webhooks.
Sometimes you may want to undo a whole commit with all changes. Instead of going through all the changes manually, you can simply tell git to revert a commit, which does not even have to be the last one. Reverting a commit means to create a new commit that undoes all changes that were made in the bad commit. Just like above, the bad commit remains there, but it no longer affects the the current master and any future commits on top of it.
git revert {commit_id}
Deleting the last commit is the easiest case. Let's say we have a remote origin with branch master that currently points to commit dd61ab32. We want to remove the top commit. Translated to git terminology, we want to force the master branch of the origin remote repository to the parent of dd61ab32:
