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

Keep alignment with plugin template via Cruft #27

Merged
merged 8 commits into from
Sep 23, 2024
Merged

Keep alignment with plugin template via Cruft #27

merged 8 commits into from
Sep 23, 2024

Conversation

justinmayer
Copy link
Contributor

The intention is to (1) bring this plugin in alignment with the latest changes to the Pelican plugin template, and (2) use Cruft to make it easier to maintain said alignment going forward.

@justinmayer justinmayer requested a review from rlaboiss July 7, 2024 21:02
@rlaboiss
Copy link
Collaborator

Hi Justin, I apologize for the big delay to get to this. Summer vacations got in the way…

I am going to merge the cruft branch and make a new release of avatar, just to be sure everything goes fine with the pipeline.

@rlaboiss rlaboiss merged commit aeba91c into main Sep 23, 2024
14 checks passed
@justinmayer justinmayer deleted the cruft branch September 23, 2024 16:07
@rlaboiss
Copy link
Collaborator

Should I migrate the other plugins that I maintain (graphviz, linkclass, and inclue-markdwon) along the same lines of the PR, as well?

@justinmayer
Copy link
Contributor Author

Yes, I think that would be beneficial. While there's no immediate imperative, bringing plugins into closer alignment with changes to the upstream plugin template will make it easier to keep them in alignment. You can use steps 2–7 of the relevant documentation to assist with this process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants