Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

auro-library: introduce script to automate library wide changes #503

Closed
Izook opened this issue Jul 10, 2023 · 1 comment
Closed

auro-library: introduce script to automate library wide changes #503

Izook opened this issue Jul 10, 2023 · 1 comment
Assignees
Labels
not-reviewed Issue has not been reviewed by Auro team members Type: Feature New Feature

Comments

@Izook
Copy link
Contributor

Izook commented Jul 10, 2023

Is your feature request related to a problem? Please describe.

It would be lovely if there was a script I could use to make an identical change across all of our component repos.

Describe the solution you'd like

Provide a customizable bash script that could make changes across all of our component repos.

Describe alternatives you've considered

Manually making changes across all of our repos.

Additional context

No response

@Izook Izook added not-reviewed Issue has not been reviewed by Auro team members Type: Feature New Feature labels Jul 10, 2023
@Izook Izook self-assigned this Jul 10, 2023
@blackfalcon
Copy link
Member

There are ways to do this, but it depends on the change. And this is not typically recommended. There was a bash I wrote that would update all the repos issues labels for example. At a certain scale, it get cumbersome and buggy.

The discussions we have been having is around building solutions that allow for updates to be added to a repo upon the next build (e.g. markdown magic) or building the update in a deliverable form like a npm package that can be versioned and easily updated.

I like the idea of making auro-library a consumable npm that makes it really easy to update internal scripts that are housed in this package.

To that end, we need to properly segment things that are templates and scripts away from things that are direct consumables so that the npm package is not heavy with unnecessary files.

@blackfalcon blackfalcon transferred this issue from AlaskaAirlines/auro-library Feb 12, 2024
@AlaskaAirlines AlaskaAirlines locked and limited conversation to collaborators Feb 12, 2024
@blackfalcon blackfalcon converted this issue into discussion #504 Feb 12, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
not-reviewed Issue has not been reviewed by Auro team members Type: Feature New Feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants