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

Regarding: https://github.com/microsoft/api-guidelines/blob/vNext/Guidelines.md
In section 14.4.4 Example Response "details" object doesn't fit the definition of "details" in section 7.10.2, table Error: Object. Details should be Error[]

{
  "error": {
    "code": "requestLimitExceeded",
    "message": "The caller has made too many requests in the time period.",
    "details": {
      

There is some noise, I need to clean it up

It should involve things such as description, sensors used, s/w requirements, h/w requirements, schematics, how to install a library in the Arduino IDE, baud rate settings, usage etc.

Refer to the various Arduino project documentations for assistance.

We found out that in some parts of Zalando several more X-headers are in use, partially set by HTTP routers. Those cause Zally-violations.

We want to check the most common violations and see which need Guideline updates.

(Internal link)

Documentation

URL(s)

• https://zeit.co/docs/v2/build-step
• https://zeit.co/docs/v2/serverless-functions/introduction
• https://zeit.co/docs/runtimes#advanced-usage/advanced-node-js-usage/custom-build-step-for-node-js
• https://zeit.co/docs/runtimes#advanced-usage/technical-details/including-additional-files

Brief Summary: The role of the build steps for static files in the pu

As Github is providing more functionality, we should think about the possibility of providing more feedback messages to the Github "Checks" Tab:

Steps for this:

• (Reseach) Current state of logging (architecture research)
• (Research) Github "

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

Description
Add a section on testing to the coding guidelines page.

We’ve got different test suites now (linting, unit, e2e) and I think it’d be good to call those out, what each one does, and what our expectations are for contributions WRT tests.

anything else to add @1Copenut ?

• I'm submitting a ...

  • feature request

• What is the current behavior?
  While we have guidelines on how to request multiple fields or embedded resources, search request section does not consider multi-value filters. OpenAPI defines different serialization options so we could mention all of them or choose one format as preferred option: https://swagger.io/docs/specification/se