Skip to content

Conversation

@bbatsov
Copy link
Collaborator

@bbatsov bbatsov commented Apr 1, 2025

@zerolfx would it be possible to merge this and push a "v0.1.0" tag afterwards?

It will address #353 and will make it easier to distribute "stable" releases to our users.

P.S. If I seem reliable enough you can consider making me a co-maintainer, so I can deal with such tasks myself as well.

@zerolfx
Copy link
Collaborator

zerolfx commented Apr 2, 2025

@bbatsov Sure! I've added you to this repo (and you can deal with this and other PRs yourself). This project does need some active maintainers.
Thanks for all your help.

@bbatsov
Copy link
Collaborator Author

bbatsov commented Apr 2, 2025

@zerolfx Thanks! Would you, please, change the repository settings to allow all PR merge options (e.g. Merge and Rebase). I see for some reason only Squash and merge is possible right now, but it's not always the best option. (e.g. you I usually want to preserve the individual commits if they are well organized)

@zerolfx
Copy link
Collaborator

zerolfx commented Apr 2, 2025

@bbatsov done

@bbatsov bbatsov merged commit dfeccc9 into copilot-emacs:main Apr 2, 2025
13 checks passed
@bbatsov
Copy link
Collaborator Author

bbatsov commented Apr 2, 2025

I've added you to this repo (and you can deal with this and other PRs yourself).

It seems I can't merge my own PRs, though. 😅 (says I don't have write access, so I still need someone to approve #399 and I'm not sure I have permissions to push tags) What are the default permissions for the contributors team?

@bbatsov bbatsov deleted the new-release branch April 2, 2025 07:38
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