Allow user to customise gci sections

[markvl-sbp]

To allow the user of these tasks to specify their own sections, I've introduced the GCI_SECTIONS variable (which is not defined on purpose).

This also fixes the mismatch between the gci and gci-write tasks where the latter did specify sections and the former did not.

[sbp-bvanb]

To allow the user of these tasks to specify their own sections, I've introduced the GCI_SECTIONS variable (which is not defined on purpose).

This also fixes the mismatch between the gci and gci-write tasks where the latter did specify sections and the former did not.

I know you mentioned: I've introduced the GCI_SECTIONS variable (which is not defined on purpose). Would it be possible to define a default anyway or does it depend on the repository name and should always be defined? Would it be an idea to update the example in the README.md as well?

[markvl-sbp]

I know you mentioned: I've introduced the GCI_SECTIONS variable (which is not defined on purpose). Would it be possible to define a default anyway

Yes, that would be a problem since, as far as I could tell from a quick experiment, I could not override the "default" via the Taskfile.yaml in my project. If there is a way, please let me know since I agree that having a default value would be nice.

or does it depend on the repository name and should always be defined?

Not sure what you mean with "depend on the repository name". But the task still works if the variable is not defined. (And that is also why I did not add a requires section.)

Would it be an idea to update the example in the README.md as well?

Sure, I can add something to the README.md. I'm thinking about a "Configuration" section within the "Taskfile" section, where I list the task, the variable and why you'd use it (and/or an example). How does that sound?

[sbp-bvanb]

I know you mentioned: I've introduced the GCI_SECTIONS variable (which is not defined on purpose). Would it be possible to define a default anyway

Yes, that would be a problem since, as far as I could tell from a quick experiment, I could not override the "default" via the Taskfile.yaml in my project. If there is a way, please let me know since I agree that having a default value would be nice.

or does it depend on the repository name and should always be defined?

Not sure what you mean with "depend on the repository name". But the task still works if the variable is not defined. (And that is also why I did not add a requires section.)

Would it be an idea to update the example in the README.md as well?

Sure, I can add something to the README.md. I'm thinking about a "Configuration" section within the "Taskfile" section, where I list the task, the variable and why you'd use it (and/or an example). How does that sound?

@markvl-sbp Could you try:

vars:
  SOMETHING: '{{.SOMETHING| default "DefaultSomething"}}'
tasks:
  hello:
    cmds:
      - |
        echo {{.SOMETHING}}

[markvl-sbp]

Could you try:

vars:
  SOMETHING: '{{.SOMETHING| default "DefaultSomething"}}'
tasks:
  hello:
    cmds:
      - |
        echo {{.SOMETHING}}

This indeed works, if you use this to override the variable:

includes:
  remote:
    taskfile: <url to this Taskfile.yml>
    vars:
      SOMETHING: 'SomethingElse'

If you simply add the SOMETHING var to the vars section in your local Taskfile.yml it will not work.

I'll update the PR (including the README) to reflect this new insight.