From: reback00 <reback00@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Please add "hacktoberfest" tag/topic
Date: Tue, 06 Oct 2020 10:44:30 +0200 [thread overview]
Message-ID: <20201006084430.TFkdAhjBqfawI2ygRosCPLy1_CFwavhkNbZ6oD-L5mE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25383@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1975 bytes --]
Closed issue by reback00 on void-packages repository
https://github.com/void-linux/void-packages/issues/25383
Description:
I just got an email describing changes for Hacktoberfest this year. They've changed the rules. Now, repositories have to manually opt-in in order to accept entries for Hacktoberfest. Either (a) a "hacktoberfest" tag/topic can be added to accept all PRs on the repo or (b) add a "hacktoberfest-accepted" tag to each PR to be accepted (which is probably impractical for this repo with so many PRs).
The email has these changes highlighted:
> After working closely with our friends at GitHub, we are happy to introduce measures that are brand new to Hacktoberfest 2020.
> 1. Pull requests can be made in any __participating__ GitHub-hosted repositories/projects.
>
> 2. Maintainers can opt-in to participate by [classifying their projects with the hacktoberfest topic](https://www.youtube.com/watch?v=FxBv4FMcDgo&ab_channel=DigitalOcean).
>
> 3. Your pull requests will count toward your participation if they are in a repository with the hacktoberfest topic and once they have been merged, approved by a maintainer or labelled as hacktoberfest-accepted.
>
> 4. Additionally, any pull request with the hacktoberfest-accepted label, submitted to any public GitHub repository, with or without the hacktoberfest topic, will be considered valid for Hacktoberfest.
> All valid pull requests prior to Oct 3 (when these rules were introduced) will be honored and counted toward completion of Hacktoberfest.
>
> __[Learn more](https://hacktoberfest.digitalocean.com/hacktoberfest-update) about the changes we've made that will affect your participation.__
I participated in previous year's Hacktoberfest with [PRs only from this repo](https://www.reddit.com/r/voidlinux/comments/dkwpvr/yaaayyy_i_completed_this_years_hacktoberfest_with/). So please add the "hacktoberfest" tag/topic so that many like me can try this year with this repo.
prev parent reply other threads:[~2020-10-06 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 8:18 [ISSUE] " reback00
2020-10-06 8:39 ` Zeinok
2020-10-06 8:44 ` reback00
2020-10-06 8:44 ` reback00 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201006084430.TFkdAhjBqfawI2ygRosCPLy1_CFwavhkNbZ6oD-L5mE@z \
--to=reback00@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).