Skip to content
Snippets Groups Projects
  1. Apr 26, 2022
    • Daniel P. Berrangé's avatar
      github: fix config mistake preventing repo lockdown commenting · 5cf434b5
      Daniel P. Berrangé authored
      
      The previous commit updated the repo lockdown config to the new
      format:
      
        commit 9b89cdb2
        Author: Alex Bennée <alex.bennee@linaro.org>
        Date:   Mon Oct 4 16:43:08 2021 +0100
      
          .github: move repo lockdown to the v2 configuration
      
      Unfortunately the config key names used were wrong, resulting in
      the repo lockdown throwing warnings:
      
        Unexpected input(s) 'pull-comment', 'lock-pull', 'close-pull',
        valid inputs are ['github-token', 'exclude-issue-created-before',
        'exclude-issue-labels', 'issue-labels', 'issue-comment',
        'skip-closed-issue-comment', 'close-issue', 'lock-issue',
        'issue-lock-reason', 'exclude-pr-created-before', 'exclude-pr-labels',
        'pr-labels', 'pr-comment', 'skip-closed-pr-comment', 'close-pr',
        'lock-pr', 'pr-lock-reason', 'process-only', 'log-output']
      
      It still locked down the pull requests, due to its default config,
      but didn't leave the friendly message explaining why.
      
      Reviewed-by: default avatarPhilippe Mathieu-Daudé <f4bug@amsat.org>
      Signed-off-by: default avatarDaniel P. Berrangé <berrange@redhat.com>
      5cf434b5
  2. Oct 12, 2021
  3. Jun 21, 2021
  4. Feb 09, 2021
  5. Apr 07, 2020
Loading