Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Create new rules for Bluesnews, Controllerpro, Gamecritics, Gamegeekdenter, Gamesandpals, Gameselectors, Gamewithyourbrain, Howinerd, PCgamer, and Siliconera.#9692

Closed
pn303 wants to merge 27 commits intoEFForg:masterfrom
pn303:master
Closed

Create new rules for Bluesnews, Controllerpro, Gamecritics, Gamegeekdenter, Gamesandpals, Gameselectors, Gamewithyourbrain, Howinerd, PCgamer, and Siliconera.#9692
pn303 wants to merge 27 commits intoEFForg:masterfrom
pn303:master

Conversation

@pn303
Copy link
Copy Markdown

@pn303 pn303 commented Apr 27, 2017

No description provided.

pn303 added 14 commits February 23, 2017 23:57
Added HTTPS Everywhere to TYM website - sample
Create a file "tym.com.xml", which adds a rule for the
"testyourmight.com" website.
* Change some of the comments for the TYM ruleset
Get latest version of HTTPS Everywhere
Delete Testyourmight rule, inefficiently written.
Delete Testyourmight rule
@pn303 pn303 closed this Apr 28, 2017
@pn303 pn303 changed the title Get latest updates from Master Create new rules for Bluesnews, Gamergeek, Controllerpro, Gamergeek, Gamecritics, Gamesandpals, etc. Apr 28, 2017
@pn303 pn303 changed the title Create new rules for Bluesnews, Gamergeek, Controllerpro, Gamergeek, Gamecritics, Gamesandpals, etc. Create new rules for Bluesnews, Controllerpro, Gamecritics, Gamegeekdenter, Gamesandpals, Gameselectors, Gamewithyourbrain, Howinerd, PCgamer, and Siliconera. Apr 28, 2017
@pn303 pn303 reopened this Apr 28, 2017
@pn303
Copy link
Copy Markdown
Author

pn303 commented Apr 28, 2017

Merge pull request #9692 @Hainish @Bisaloo @J0WI @afarrow. Rulesets created for Eventhubs and Gamerswithjobs.

@J0WI
Copy link
Copy Markdown
Contributor

J0WI commented Apr 29, 2017

Could you please open one separate PR for each new ruleset?

@pn303
Copy link
Copy Markdown
Author

pn303 commented Apr 29, 2017

Sure, will do. Just need to play around a bit and see how to do it.

@J0WI
Copy link
Copy Markdown
Contributor

J0WI commented Apr 29, 2017

You should use a new branch for each new ruleset.

@pn303
Copy link
Copy Markdown
Author

pn303 commented Apr 29, 2017

Ok, thank you for the information

@pn303
Copy link
Copy Markdown
Author

pn303 commented Apr 29, 2017

I might have to delete my repository and start a new one, so that things can be done again properly. What I did not quite get is the branches for every new ruleset. For example, if I have made 15 rulesets, do I need to have 15 separate branches for each and send pull request from each branch separately, or I can have one branch for all of my new rulesets, but have them as different commits?

@pn303 pn303 closed this Apr 29, 2017
@J0WI
Copy link
Copy Markdown
Contributor

J0WI commented Apr 30, 2017

You need 15 separate branches and pull requests.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants