Skip to content

Conversation

@blakewatters
Copy link
Contributor

Switched the pyenv-action over to a forked version that can install Python v3.9.11. PR sent upstream but no idea how responsive the maintainer is

…on v3.9.11

Sent PR to the upstream maintainer
Copy link
Contributor

@linkous8 linkous8 left a comment

Choose a reason for hiding this comment

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

Please use the latest gabriel falcao release

@blakewatters
Copy link
Contributor Author

Why can't you just do it? Aren't you the maintainer with the broken build?

It's silly that you are all comfortable utilizing a repository from some random dude that you've never met off his personal GitHub account versus mine but yeah let's keep it "professional" and "official" even though he just merged my PR and the code is literally identical.

BTW I'm in touch with the the maintainer and we are moving this action onto an organization so I can just maintain it no PRs required. Won't that make your life easier?

@blakewatters
Copy link
Contributor Author

Done.

key: ${{ runner.os }}-pyenv
- name: Install pyenv versions
uses: blakewatters/pyenv-action@v9
uses: gabrielfalcao/pyenv-action@v9
Copy link
Contributor

Choose a reason for hiding this comment

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

@blakewatters
Copy link
Contributor Author

Done. Thanks for the support.

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