citool: Rename workflows to triggers

[lukaszcl]

---

Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.

Why

The changes focus on standardizing terminology and functionality related to how tests are triggered within the CI tool. By replacing the term "Workflows" with "Triggers", the modifications aim to clarify the mechanism that initiates test execution, making it more intuitive for users to understand and configure their CI pipelines. This adjustment enhances the readability and maintainability of the codebase by ensuring consistency in the naming conventions used across the tool.

What

• tools/citool/cmd/csv_export_cmd.go

  • Changed CSV header from "Workflows" to "Triggers" and updated variable names accordingly. This change affects how test configuration data is exported to CSV, making the output more accurately reflect the terminology used in the CI tool.
  • Effect: Aligns exported CSV column headers with the updated terminology, improving clarity for users.

• tools/citool/cmd/filter_cmd.go

  • Updated the filter logic to match tests based on "Triggers" instead of "Workflows". This modification impacts how tests are selected for execution based on specified criteria such as workflow names or triggers.
  • Effect: Ensures that the filtering feature operates with the updated terminology, maintaining the functionality's integrity.

• tools/citool/cmd/filter_cmd_test.go

  • Adjusted test cases to use "Triggers" instead of "Workflows". This change is necessary to ensure that unit tests accurately assess the functionality of the filtering logic with the new terminology.
  • Effect: Keeps unit tests in sync with the application logic, verifying that changes do not break existing functionality.

• tools/citool/cmd/types.go

  • Modified the CITestConf struct to replace "Workflows" with "Triggers" in both the field name and the comment description. This alteration reflects the broader change in terminology throughout the codebase.
  • Effect: Updates the internal data model to be consistent with the new naming convention, aiding in code comprehension and future maintenance.

[cl-sonarqube-production]

Quality Gate passed

Issues
1 New issue
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube