fix: Remove build:id in generic examples

[laurentsimon]

No description provided.

[olivekl]

In this case I'd label them, yes, because it's otherwise hard to parse visually. BUT: I'd suggest taking the steps out of the comments entirely and having them in regular text, followed by the code example for that step. That way it's very clear (visually) to the user what the steps are when glancing over the docs, and they're only copying code comments into their system that are descriptive info reminding them of what the code does.

[laurentsimon]

In this case I'd label them, yes, because it's otherwise hard to parse visually. BUT: I'd suggest taking the steps out of the comments entirely and having them in regular text, followed by the code example for that step. That way it's very clear (visually) to the user what the steps are when glancing over the docs, and they're only copying code comments into their system that are descriptive info reminding them of what the code does.

So you mean something like the following, instead of inlining the comments in the code:

• Step 1: add bla to your code

uses: builder@v1.2

• Step 2: add bla 2 to your code

jobs:
  id: bla

[olivekl]

So you mean something like the following, instead of inlining the comments in the code:

• Step 1: add bla to your code

uses: builder@v1.2

Exactly.

[laurentsimon]

So you mean something like the following, instead of inlining the comments in the code:

• Step 1: add bla to your code

uses: builder@v1.2

Exactly.

I've made the changes. Thank you both for the feedback.

[ianlewis]

Thanks @olivekl !