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

Add support for eza as a replacement for exa #1729

Merged
merged 1 commit into from
Sep 21, 2023
Merged

Conversation

azuline
Copy link
Contributor

@azuline azuline commented Sep 20, 2023

exa is unmaintained (see https://github.com/ogham/exa), and https://github.com/eza-community/eza is the community-maintained successor.

This PR adds support for eza as a replacement to exa.

Copy link
Collaborator

@N-R-K N-R-K left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fine but I'm confused as to why they made a new fork with a different name instead of continuing on the exa repository? It seems like other people have commit access to it, so what was the problem?

@jarun
Copy link
Owner

jarun commented Sep 21, 2023

Maybe for more control on the development cycle...

@jarun jarun merged commit 09bf8fe into jarun:master Sep 21, 2023
7 checks passed
@jarun
Copy link
Owner

jarun commented Sep 21, 2023

Thank you!

@azuline azuline deleted the eza branch September 21, 2023 12:58
@github-actions github-actions bot locked and limited conversation to collaborators Oct 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants