Description

Create a JSON schema to allow code editors to parse the .vela.yml and help users understand if the format is valid or not.

The simple steps to test the JSON schema:

1. convert complex .vela.yml from yaml to json
2. utilize https://jsonschema.net/home to create JSON schema
3. follow editor specific instructions to utilize the schema for .vela.yml
   • VScode docs https://code.visualstudio.com/docs/languages/json#_json-schemas-and-settings

Definition of Done

Users able to configure code editor to utilize published JSON schema for file validation

Effort (Optional)

2 days

Impacted Personas (Optional)

All users modifying .vela.yml within any code editor

Description

Update the ruleset to allow include and exclude logic for path.

Value

Greatly simplifies scenarios where you want to exclude a specific file(s) or folder(s), and not need to call out includes for everything else.

Design

Both of the below proposed design changes to the .vela.yml would have the same underlying results of:

• Commit that changes cool-code/foo.js will trigger
• Commit that changes cool-code/docs/foo.md will not trigger

proposed option 1

Add ignore and include underneath path to allow the following configuration:

ruleset:
  path: 
    include:
      - [ "cool-code/**" ]
    exclude:
      - [ "cool-code/docs/**"]

This could lead to breaking behavior due to the current structure of the yaml so extra consideration is needed.

proposed option 2

Utilize some ignore character(s) to allow updating the existing path to handle both scenarios. The following example utilizes the ignore character of !:

ruleset:
  path: [ "!cool-code/docs/**", "cool-code/** ]

Definition of Done

ruleset for path updated to allow include and exclude logic

Effort (Optional)

1 day

Impacted Personas (Optional)

All users utilizing the ruleset of path

Description

What is your idea?

Update our gopkg.in/yaml library to the v3 functionality.

https://github.com/go-yaml/yaml/tree/v3

Value

Why is this important? Who does it impact? Will this make something better, faster, etc?

• Reduce technical debt

Definition of Done

What is the end goal of this story?

This repo is using the v3 release of the gopkg.in/yaml library.

Effort (Optional)

Estimated effort to complete this story? (Best Guess e.g. 1-2 days)

N/A

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update all non-major dependencies (codecov/codecov-action, github/codeql-action, go)

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (github>whitesource/merge-confidence:beta)

Description

Current ruleset matching utilizes a file match pattern utility. This does not allow for more stringent matching, particularly with version tags. Use regex pattern matching since it allows for greater control and it commonly known.

Value

Allows more control over step ruleset matchers

Definition of Done

Current ruleset must have one or more exclude clause to eliminate greedy matches for tags with trailing data. e.g. -SNAPSHOT, -rc, -prod, etc.

    ruleset:
      if:
        event: [ tag ]
        tag: [ "[0-9].*" ]
      unless:
        event: [ tag ]
        tag: [ "[0-9].*-prod" ]

After enhancement regex can be used to explicitly identify start/end of match

if:
  branch: master
  event: tag
  tag: [ "^refs/tags/(\\d+\\.)+\\d+$" ]

Effort (Optional)

4 days

Impacted Personas (Optional)

Users