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

BUG: Don't exclude .gp class by default #188

Merged
merged 1 commit into from
Nov 18, 2022

Conversation

rkdarst
Copy link
Collaborator

@rkdarst rkdarst commented Nov 17, 2022

- Immediate fix to backwards compatibility of executablebooks#185.
- I'm not implying I wouldn't want to change the default later.
Copy link
Member

@choldgraf choldgraf left a comment

Choose a reason for hiding this comment

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

I'm +1 on just merging this so that we preserve old behavior. Let's do that and we can be deliberate about changing behavior back in the future.

@rkdarst are you interested in having merge rights on this repo so that you can make releases as well?

@choldgraf choldgraf changed the title sphinx_copybutton/__init__: Don't exclude .gp class by default BUG: Don't exclude .gp class by default Nov 18, 2022
@choldgraf choldgraf merged commit 093defe into executablebooks:master Nov 18, 2022
@rkdarst
Copy link
Collaborator Author

rkdarst commented Nov 18, 2022

I'm quite happy without any special access here! I would also be happy to help out, if someone ever called on me. But I am so busy with other things, that I worry you would put effort so that I can do something, and then never have time. Better to rely on me as a drive-by contributor until something more is needed. let me know, you know how to find me...

@rkdarst rkdarst deleted the exclude_no_gp branch November 18, 2022 16:33
@choldgraf
Copy link
Member

From my perspective, I would like to increase the bus factor across this repository and many others in the executable books stack. We are critically under resourced for such a heavily-used stack so need all the help we can get.

@rkdarst
Copy link
Collaborator Author

rkdarst commented Nov 20, 2022

yeah, I understand. I'll try coming to the next executiblebooks meeting. I could easily use the workflow file and do a release, but learning other release practices would take more time (docs, etc). I'm still not sure if it's worth it for me to try to get involved short-term unless there are current emergencies.

@choldgraf
Copy link
Member

I don't think you should feel compelled to be involved - we are all volunteers with only a couple exceptions from the initial grant. But just wanted to emphasize that from my perspective any contribution is welcome 🙂

@rkdarst
Copy link
Collaborator Author

rkdarst commented Dec 5, 2022

Perhaps I was at the wrong place for the most recent executablebooks meeting. Or perhaps it didn't happen. Anyway, I would be happy to talk synchronously about how we can better work together on Sphinx stuff - let me know.

@choldgraf
Copy link
Member

I believe that @rowanc1 did in-fact lead the meeting. Where did you go to attend @rkdarst ?

@rowanc1
Copy link
Member

rowanc1 commented Dec 6, 2022

Yes, we did have the meeting! I didn't do a great job of advertising beforehand though. We mostly talked through MyST enhancement proposals and ways to coordinate some of our development practices.

Would be happy to have you there next time!!

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.

None yet

4 participants