Skip to content

[BUG]: Repository JSON null but Config YAML not #31

Closed
@actuarysailor

Description

@actuarysailor

Describe the bug
If the Config settings are not null, but the settings in the YAML are you get errors when it tries to reference values in the repo settings.

To Reproduce
Steps to reproduce the behavior:

  1. Set all your PR Options in a repo to none - remove all status checks, overrides, etc.
  2. Configure Settings.YAML to populate status checks and who can close / override pull request options etc.
  3. Run the action'
  4. See error

Expected behavior
It should show them as a difference rather than throwing an error because a dictionary key is missing.

Screenshots
Sorry, didn't take any, but provided steps to reproduce.

Desktop (please complete the following information):

  • OS: Win10
  • Browser Edge
  • Version 101.0.1210.39 (Official build) (64-bit)

Additional context
Came across it when I was testing the PR for status checks. That PR has this fixed.
Fixed in #28

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions