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

Hacktoberfest 2021 #2681

Closed
Bibo-Joshi opened this issue Sep 30, 2021 · 0 comments
Closed

Hacktoberfest 2021 #2681

Bibo-Joshi opened this issue Sep 30, 2021 · 0 comments

Comments

@Bibo-Joshi
Copy link
Member

Bibo-Joshi commented Sep 30, 2021

Update

We have created a Telegram group chat that is intended for questions regarding the development of PTB. More info can be found here. You very welcome to join if you have questions regarding your Hacktoberfest contribution!


Original Post

In some parts of the world it's already 1st of October and this means: It's time for Hacktoberfest! 💻🥨

Hacktoberfest is an event that encourages open source developers to contribute to repositories through pull requests. If you ever thought about starting coding or giving back to your favourite open source repositories, now is the time! Head over to the hacktoberfest website to learn more about it.

Of course, this is also a great opportunity to contribute to python-telegram-bot 🙂 We already prepared some issues on our repositories, but feel free to begin a hunt for improvements and fixes by yourself! We'd like to especially point out issue #2633, which is about improving our documentation. This issue has several aspects that can be tackled in multiple pull requests and it's great for first time contributors.

⚠️ If you want to tackle an issue, please be sure to

  • first comment on that issue so that we can assign you to it and avoid duplicate pull requests for the same issue by several people.

  • read this version of the contribution guide

  • base your branch on the v14 branch and not on the master branch as described below. This is important, as we're currently working towards a breaking release and the v14 branch already contains some notable changes from master. To base your branch on v14, replace

    $ git fetch upstream
    $ git checkout master
    $ git merge upstream/master
    $ git checkout -b your-branch-name

    with

    $ git fetch upstream
    $ git checkout v14
    $ git merge upstream/v14
    $ git checkout -b your-branch-name

    in the contribution guide.

@Bibo-Joshi Bibo-Joshi pinned this issue Sep 30, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Oct 1, 2021
@harshil21 harshil21 unpinned this issue Dec 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant