In 1.2, we can read the following:

You can use --autosquash to squash all your commits to a single commit. Nobody wants many commits for a single feature in develop branch. read more...

I think that asserting that nobody wants that is a fallacy. There are good reasons for which you would want to keep those commits separated even in develop branch:

• know what the reason of a change wa

Your example of a well structured URL:

https://api.contoso.com/v1.0/people/jdoe@contoso.com/inbox

in URL Structure includes PII in the URL which is prohibited in PII parameters

There is some noise, I need to clean it up

I love base16, but it took me a long time to figure out what's useful about it. For me, the killer feature is being able to configure things once -- either with a base16 plugin like for vim, or just sticking to the 8 ANSI colors for simpler things like tmux -- and then switch color themes in everything with a single click in my terminal emulator preferences. It all immediately updates, even in v

Refer to:

1. commit-message-guidelines - robertpainsi
2. Follow these git commit message guidelines - theserverside
3. [Writing good commit messages](https://github.com/erlang/otp/wiki/writing-good-commit

When looking on how services usually handle variations of paths, we can see big differences between different frameworks and service implementations, which is not reflected in the API specification but has a negative impact on predictability of the behavior of an API and the way how it is or can be used. The keyword here is request path normalization, i.e.

1. How are adjacent slashes in a reque

Guide Request

Subject: Guide & example for running unit & integration tests on deployment

Additional Information

I'd love to see a clear guide, with examples, of unit & integration tests running on each deployment. There doesn't seem to be any mention of automated testing, (outside of bugbear) in the existing guides.

Examples in no_if erl have different conditions betwen bad/1 and better/1, good/1. It needs to correct and extend.

bad(Connection) ->
  {Transport, Version} = other_place:get_http_params(),
  if
    Transport =/= cowboy_spdy, Version =:= 'HTTP/1.1' ->
      [{<<"connection">>, utils:atom_to_connection(Connection)}];
    true ->
      []
  end.

When we start using xibs we will have to name the IBAction methods and the corresponding delegate methods to the ViewController

@IBAction func didPressLogin(_ sender: Any)

In the spirit of this article: http://khanlou.com/2016/09/swifty-delegates/ we agreed on naming the delegates like this:

func didPressLogin(on authView: UIView)

The current editable template is a great start. It's right there and you just have to edit it, like you do with your README.md in your editor. (That's a little nerdy, but not elitist, so i would keep that design. I think programmers love it!) You don't have to install anything and have a preview next to it.

We should extend it in a way so it still feels this lightwight.

I like the idea to ha

Describe the bug
Core is using a version of react-aria-modal which has an open issue to fix using componentWillMount method. This is currently deprecated.

Track the progress of that component here: davidtheclark/react-aria-modal#93 to know when to update appropriately.