Do not want GitHub issues tile

[dshuffma-ibm]

I don't want the GitHub issues tile in my toolchain. I've set has_issues to false but when I create the chain, the issues tile is created each time...

toolchain.yml:

version: '2'
messages:
  $i18n: locales.yml
template:
  name:
    $ref: "#/messages/template.name"
  description:
    $ref: "#/messages/template.description"
  header: '![](toolchain.png)'
  icon: icon.svg
  required:
    - sample-build
    - sample-repo
  info:
    git url: >-
      [https://github.com/dshuffma-ibm/marbles](https://github.com/dshuffma-ibm/marbles)
    git branch: >-
      [master](https://github.com/dshuffma-ibm/marbles/tree/master)
toolchain:
  name: 'marbles-toolchain-{{timestamp}}'
  template:
    getting_started:
      $ref: "#/messages/template.gettingStarted"
services:
  sample-repo:
    service_id: githubpublic
    parameters:
      repo_name: '{{toolchain.name}}-repo'
      repo_url: 'https://github.com/dshuffma-ibm/marbles'
      type: clone
      has_issues: false
      enable_traceability: true
  sample-build:
    service_id: pipeline
    parameters:
      services:
        - sample-repo
      name: '{{services.sample-repo.parameters.repo_name}}'
      ui-pipeline: true
      configuration:
        content:
          $text: pipeline.yml
        env:
          SAMPLE_REPO: sample-repo
          CF_APP_NAME: '{{form.pipeline.parameters.prod-app-name}}'
          PROD_SPACE_NAME: '{{form.pipeline.parameters.prod-space}}'
          PROD_ORG_NAME: '{{form.pipeline.parameters.prod-organization}}'
          PROD_REGION_ID: '{{form.pipeline.parameters.prod-region}}'
        execute: true
form:
  pipeline:
    parameters:
      prod-app-name: '{{services.sample-repo.parameters.repo_name}}'
    schema:
      $ref: deploy.json

[dshuffma-ibm]

I might have fixed this by toggling the issues checkbox on and back off.... It seems to be staying off now.

[hmagph]

The template itself should honour the setting still.

[gmarjoram]

@dshuffma-ibm I cannot reproduce this problem on production. I've tried with my own toolchain.yml and the has_issues option is being honoured as far as I can tell.

What I have noticed however is that there is a time lag from when I commit a change to the toolchain.yml in my repo to when it shows up on raw.githubusercontent.com (which is what is used by the toolchain code to get the file from github). I presume that github are employing some sort of caching mechanism here. Is it possible that when you are changing the has_issues option that the change has just not flushed through to raw.githubusercontent.com yet ?

If not maybe you can give me the exact steps you're using to reproduce this at your end.

[Jaorji]

I'm pretty sure this is a Github cache issue. I see this every time when I change my pipeline template. What I usually do is creating a branch when I have changes or just wait for a moment until the change shows up. So I don't think this is a problem for us.

[dshuffma-ibm]

We no longer use toolchain, and I don't have things in place to reproduce. You can can close, i'm not concerned.

The cache suggestion makes sense. Not sure if this is your cache or not, but it would have been nice to disable that when developing.