Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert CI data variables into json/yaml #1015

Open
rob1997 opened this issue Jun 10, 2024 · 0 comments
Open

Convert CI data variables into json/yaml #1015

rob1997 opened this issue Jun 10, 2024 · 0 comments
Assignees
Labels
Type: Enhancement Added to issues and PRs when a change includes improvements or optimizations.

Comments

@rob1997
Copy link
Collaborator

rob1997 commented Jun 10, 2024

Summary
currently data for CI in scripts/data all are in a .txt format

Suggested features or ways to address the summary
Convert these data to json/yaml and read via bash

Motivation

  • Current implementation is a sure way to run into unreadable and difficult to solve merge conflicts
  • json/yaml are more More readable formats and easier for editing/introducing new changes

Acceptance Criteria
CI functions as before with CI data converted to a new file format.

Blockers
(OPTIONAL) [Do you see any blocker that needs to be done before implementing this feature?]

Dependencies
(OPTIONAL) [Do you know about dependencies that directly affect this issue?]

Additional Context
(OPTIONAL) [Add any other context, files, images (screenshots/videos), diagrams, or documents about the feature request here.]

Final Steps

  • Give it one of these labels Type: Feature Type: Enhancement
  • Add your estimation

Estimations

| 3 | Mild efort | A day | Low complexity | Low |

@rob1997 rob1997 added the Type: Enhancement Added to issues and PRs when a change includes improvements or optimizations. label Jun 10, 2024
@rob1997 rob1997 self-assigned this Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Added to issues and PRs when a change includes improvements or optimizations.
Projects
None yet
Development

No branches or pull requests

1 participant