Rules of protection. Protection in Magic: The Gathering – Rules, History, and Strategies

What are the key aspects of protection in Magic: The Gathering. How has protection evolved throughout the game’s history. What strategies can players employ when using or facing protection abilities.

Understanding Protection in Magic: The Gathering

Protection is a powerful keyword ability in Magic: The Gathering that grants a range of defensive benefits to creatures, players, or other permanents. This ability has been a part of the game since its inception and continues to play a significant role in gameplay strategies and deck construction.

The core concept of protection can be summarized using the acronym DEBT:

• Damage: The protected entity cannot be damaged by sources with the specified quality.
• Enchant/Equip: The protected entity cannot be enchanted, equipped, or fortified by permanents with the specified quality.
• Block: The protected creature cannot be blocked by creatures with the specified quality.
• Target: The protected entity cannot be targeted by spells or abilities from sources with the specified quality.

The Evolution of Protection in MTG

Protection has undergone several changes throughout Magic: The Gathering’s history. Initially introduced in Alpha, it has been a constant presence in the game, though its status as an evergreen mechanic has fluctuated.

Key Milestones in Protection’s History

1. Alpha (1993): Protection introduced as a core mechanic
2. Sixth Edition (1999): Removed from core sets
3. Ninth Edition (2005): Reintroduced to core sets
4. Magic Origins (2015): Demoted from evergreen to deciduous status
5. Modern Horizons (2019): Notable reappearance
6. Core Set 2020 (2019): Returned to evergreen status on a probationary basis
7. 2021: Officially reinstated as an evergreen mechanic

The Mechanics of Protection in Detail

How does protection function in gameplay? Protection is defined by a specific set of rules that determine its interactions with various game elements.

Damage Prevention

When a permanent or player has protection from a quality, all damage that would be dealt to it by sources with that quality is prevented. This includes both combat damage and damage from spells or abilities.

Aura, Equipment, and Fortification Restrictions

Permanents with protection cannot be enchanted by Auras, equipped by Equipment, or fortified by Fortifications that have the specified quality. If such an attachment is already in place when protection is gained, it will fall off.

Blocking Limitations

Creatures with protection from a quality cannot be blocked by creatures with that quality. This creates opportunities for unblockable attacks in certain matchups.

Targeting Immunity

Spells and abilities from sources with the specified quality cannot target the protected permanent or player. This provides a significant defense against removal spells and targeted effects.

Strategic Applications of Protection

How can players leverage protection abilities to their advantage? Protection offers various strategic benefits in both offensive and defensive situations.

Offensive Strategies

• Evasion: Use creatures with protection to bypass blockers of a specific color or type
• Voltron tactics: Build up a single creature with multiple protections to create a formidable attacker
• Color hosing: Employ protection from a specific color to shut down mono-colored strategies

Defensive Applications

• Spell immunity: Protect key creatures or permanents from removal spells
• Damage prevention: Use protection to nullify damage-based board wipes or combat tricks
• Aura/Equipment control: Prevent opponents from enhancing their creatures against your protected permanents

Protection Variants and Special Cases

Are there different types of protection abilities? While the basic concept of protection remains consistent, several variants and special cases exist within the Magic: The Gathering rules.

Protection from Everything

Some cards, like Progenitus, have “protection from everything.” This comprehensive protection applies to all colors, card types, and other characteristics, making the permanent nearly invulnerable.

Protection from Players

Certain cards grant protection from specific players, such as True-Name Nemesis. This unique form of protection prevents the chosen player from interacting with the protected permanent in almost any way.

Protection from Converted Mana Cost

Some cards offer protection based on converted mana cost (now called mana value), like Seht’s Tiger. This allows for more flexible protection that can change dynamically during the game.

Countering and Overcoming Protection

How can players deal with protected permanents? While protection is a powerful ability, it’s not without weaknesses. Several strategies and card effects can help overcome or bypass protection.

• Board wipes: Effects that don’t target or deal damage, like “destroy all creatures,” can still affect protected permanents
• Sacrifice effects: Forcing an opponent to sacrifice a creature bypasses protection
• -1/-1 counters: These can reduce a protected creature’s toughness to 0 without dealing damage
• Indirect targeting: Spells or abilities that don’t directly target the protected permanent can still affect it
• Colorless sources: Protection from a color doesn’t prevent interaction from colorless spells or abilities

Protection in Different Magic Formats

How does the role of protection vary across different Magic: The Gathering formats? The impact and prevalence of protection can differ significantly depending on the format being played.

Standard

In Standard, protection appears less frequently due to its deciduous status. When present, it often serves as a powerful sideboard option against specific strategies or as a build-around mechanic for certain archetypes.

Modern and Legacy

These eternal formats have access to a wider range of protection effects, including some of the most powerful ever printed. Protection plays a crucial role in many sideboards and can be a key factor in certain matchups.

Commander

In the multiplayer Commander format, protection can be a double-edged sword. While it provides strong defenses, it can also lead to feel-bad moments if it completely shuts down another player’s strategy. As a result, many Commander players use protection judiciously.

The Future of Protection in Magic: The Gathering

What can we expect for protection in upcoming Magic: The Gathering sets? While predicting exact card designs is impossible, we can make some educated guesses based on recent trends and developer comments.

• Continued presence: As an evergreen mechanic, protection is likely to appear regularly in future sets
• Innovative applications: Designers may explore new ways to use protection, such as temporary or conditional protection effects
• Balancing act: Expect to see protection used carefully to avoid creating overpowered or unfun gameplay scenarios
• Format considerations: The frequency and power level of protection effects may vary depending on the needs of different formats

As Magic: The Gathering continues to evolve, protection remains a fundamental part of the game’s strategy and design space. Its ability to create interesting gameplay decisions and powerful effects ensures that it will continue to be a relevant and exciting mechanic for years to come.

Protection – MTG Wiki

in:
Keywords/Static, Glossary

Edit this Page

Protection from [quality] is an evergreen keyword ability that grants several different effects to the permanent or player it is affecting. ^[2]

The definition of protection, and the rules backing it, have changed over the course of the game’s history.

Contents

• 1 Description
• 2 History
• 3 Rules
  • 3.1 Variants
• 4 Examples
• 5 References
• 6 External links

Description[]

This ability represents a magical resistance to certain types of magic, often a specific color.^[3] It was introduced in Alpha and saw frequent use through Magic Origins. Protection was previously dropped from evergreen status to deciduous status but as of 2021 is officialy back to evergreen status. It’s an ability primary in white that can show up in other colors, usually with protection from something the color dislikes (an enemy color, artifacts for green, etc.).^[4]

Protection is commonly misunderstood as complete exemption from permanents, and effects created by cards, with the specified quality. However, protection is defined by a relatively narrow set of rules, which are often communicated using the mnemonic acronym DEBT. The permanent or player with protection cannot be:

• Damaged by sources with the specified quality. (All such damage is prevented.)
• Enchanted, equipped, or fortified by permanents with the specified quality.
• Blocked by creatures with the specified quality.
• Targeted by spells with the specified quality, or by abilities from sources of that quality.

The current (as of Core Set 2020) reminder text for protection largely reflects this, reading “This [object] can’t be blocked, targeted, dealt damage, enchanted, or equipped by anything [quality].”

History[]

Despite intuitive expectations for the keyword, protection was recognized as potentially complicated even prior to the game’s release. Early attempts to define protection led the Alpha designers to invent the fundamental concept of targeting.^[5] However, even the original rulebook described it informally, offering only examples of things that protection would prevent. ^[6]

A creature with protection from one or more colors of magic cannot be affected by any magic of those colors. For example, a creature with protection from blue cannot be blocked by blue creatures, dealt damage by blue creatures, or enchanted, damaged, or otherwise affected by blue cards. Damage done by such a creature cannot be prevented using blue cards. Note that the creature does not have this ability until it is successfully summoned. If, for example, you are summoning a creature with protection from blue magic, your rival can still cast a blue interrupt that affects the summoning spell.

Protection was excluded from core sets beginning with Sixth Edition and returned to them in Ninth Edition, reflecting concerns about its complexity for newer players. With the release of Magic Origins, protection was demoted from evergreen to deciduous, relegating it to only occasional use.^[7][8] In the three blocks following that decision, it was used only once: on Emrakul, the Promised End.

Later, it reappeared in Modern Horizons.^[9] It also returned in Core Set 2020, where it was back to evergreen on a probationary status.^[2][10][11] Although it doesn’t show up in every set, protection became officially evergreen again in 2021.^[12][13]

Two white cards have a condensed version of Protection: Sungold Sentinel and Skrelv, Defector Mite. Both have an activated ability that grants hexproof from a color and prevent blocking by creatures of that color, making up about half of protection’s text and most of its gameplay. As with many gameplay design choices, the “prevent damage” aspect is left out as to avoid the “infinite blocking” scenario.

Rules[]

From the glossary of the Comprehensive Rules (June 16, 2023—The Lord of the Rings: Tales of Middle-earth)

Protection

A keyword ability that provides a range of benefits against objects with a specific quality. See rule 702.16, “Protection.”

From the Comprehensive Rules (June 16, 2023—The Lord of the Rings: Tales of Middle-earth)

• 702.16. Protection
  • 702.16a Protection is a static ability, written “Protection from [quality].” This quality is usually a color (as in “protection from black”) but can be any characteristic value or information. If the quality happens to be a card name, it is treated as such only if the protection ability specifies that the quality is a name. If the quality is a card type, subtype, or supertype, the ability applies to sources that are permanents with that card type, subtype, or supertype and to any sources not on the battlefield that are of that card type, subtype, or supertype. This is an exception to rule 109.2.
  • 702.16b A permanent or player with protection can’t be targeted by spells with the stated quality and can’t be targeted by abilities from a source with the stated quality.
  • 702.16c A permanent or player with protection can’t be enchanted by Auras that have the stated quality. Such Auras attached to the permanent or player with protection will be put into their owners’ graveyards as a state-based action. (See rule 704, “State-Based Actions.”)
  • 702.16d A permanent with protection can’t be equipped by Equipment that have the stated quality or fortified by Fortifications that have the stated quality. Such Equipment or Fortifications become unattached from that permanent as a state-based action, but remain on the battlefield. (See rule 704, “State-Based Actions.”)
  • 702.16e Any damage that would be dealt by sources that have the stated quality to a permanent or player with protection is prevented.
  • 702.16f Attacking creatures with protection can’t be blocked by creatures that have the stated quality.
  • 702.16g “Protection from [quality A] and from [quality B]” is shorthand for “protection from [quality A]” and “protection from [quality B]”; it behaves as two separate protection abilities. If an effect causes an object with such an ability to lose protection from [quality A], for example, that object would still have protection from [quality B].
  • 702.16h “Protection from all [characteristic]” is shorthand for “protection from [quality A],” “protection from [quality B],” and so on for each possible quality the listed characteristic could have; it behaves as multiple separate protection abilities. If an effect causes an object with such an ability to lose protection from [quality A], for example, that object would still have protection from [quality B], [quality C], and so on.
  • 702.16i “Protection from each [set of characteristics, qualities, or players]” is shorthand for “protection from [A],” “protection from [B],” and so on for each characteristic, quality, or player in the set. It behaves as multiple separate protection abilities.
  • 702.16j “Protection from everything” is a variant of the protection ability. A permanent or player with protection from everything has protection from each object regardless of that object’s characteristic values. Such a permanent or player can’t be targeted by spells or abilities and can’t be enchanted by Auras. Such a permanent can’t be equipped by Equipment, fortified by Fortifications, or blocked by creatures. All damage that would be dealt to such a permanent or player is prevented.
  • 702.16k “Protection from [a player]” is a variant of the protection ability. A permanent or player with protection from a specific player has protection from each object that player controls and protection from each object that player owns not controlled by another player, regardless of that object’s characteristic values. Such a permanent or player can’t be targeted by spells or abilities the specified player controls and can’t be enchanted by Auras that player controls. Such a permanent can’t be equipped by Equipment that player controls, fortified by Fortifications that player controls, or blocked by creatures that player controls. All damage that would be dealt to such a permanent or player by sources controlled by the specified player or owned by that player but not controlled by another player is prevented.
  • 702.16m Multiple instances of protection from the same quality on the same permanent or player are redundant.
  • 702.16n Some Auras both give the enchanted creature protection from a quality and say “this effect doesn’t remove” either that specific Aura or all Auras. This means that the specified Auras aren’t put into their owners’ graveyards as a state-based action. If the creature has other instances of protection from the same quality, those instances affect Auras as normal.
  • 702.16p One Aura (Benevolent Blessing) gives the enchanted creature protection from a quality and says the effect doesn’t remove certain permanents that are “already attached to” that creature. This means that, when the protection effect starts to apply, any objects with the stated quality that are already attached to that creature (including the Aura giving that creature protection) will not be put into their owners’ graveyards as a state-based action. Other permanents with the stated quality can’t become attached to the creature. If the creature has other instances of protection from the same quality, those instances affect attached permanents as normal.

Variants[]

Protection is written in the form “protection from…”, followed by one or more qualities or characteristics. The first examples of protection are from colors, but many other variants have been printed.

Last Updated for Core Set 2021

1. ↑ ^{a b} Tsabo Tavoc originally had “protection from Legends”, but this was errataed to “protection from legendary creatures” when “Legend” ceased to be a creature subtype.

Examples[]

Example

White Knight
Creature — Human Knight
2/2
First strike (This creature deals combat damage before creatures without first strike.)
Protection from black (This creature can’t be blocked, targeted, dealt damage, or enchanted by anything black.)

References[]

1. ↑ Mark Rosewater (March 28, 2022). “Deciduous”. magicthegathering.com. Wizards of the Coast.
2. ↑ ^{a b} Mark Rosewater (June 18, 2019). “Did R&D change their mind on protection being removed from evergreen?”. Blogatog. Tumblr.
3. ↑ Mark Rosewater (May 29, 2019). “If a creature has protection from a color will that protection prevent effects such as Infest?”. Blogatog. Tumblr.
4. ↑ Mark Rosewater (June 5, 2017). “Mechanical Color Pie 2017”. magicthegathering.com. Wizards of the Coast.
5. ↑ Brady Dommermuth (June 01, 2009). “Mechanically Inclined”. magicthegathering.com. Wizards of the Coast.
6. ↑ John Carter (December 25, 2004). “The Original Magic Rulebook”. magicthegathering.com. Wizards of the Coast.
7. ↑ Mark Rosewater (June 8, 2015). “Evergreen Eggs & Ham”. magicthegathering.com. Wizards of the Coast.
8. ↑ Mark Rosewater (August 06, 2017). “I noticed that there have been very few cards with “Protection” in recent sets.”. Blogatog. Tumblr.
9. ↑ Matt Tabak (May 31, 2019). “Modern Horizons Mechanics”. magicthegathering.com. Wizards of the Coast.
10. ↑ Mark Rosewater (June 18, 2019). “Protection is back? i mean, i love that, but how come?”. Blogatog. Tumblr.
11. ↑ Mark Rosewater (June 24, 2019). “Core Than Meets The Eye”. magicthegathering.com. Wizards of the Coast.
12. ↑ Mark Rosewater (October 18, 2021). “Mechanical Color Pie 2021 Changes”. magicthegathering.com. Wizards of the Coast.
13. ↑ Mark Rosewater (March 28, 2022). “Deciduous”. magicthegathering.com. Wizards of the Coast.

External links[]

• A Planeswalker’s Primer for Magic 2011: Protection (Video). Magic: The Gathering. YouTube.

Community content is available under CC BY-NC-SA 2.5 unless otherwise noted.

• Fantasy

Protection – MTG Wiki

in:
Keywords/Static, Glossary

Edit this Page

Protection from [quality] is an evergreen keyword ability that grants several different effects to the permanent or player it is affecting. ^[2]

The definition of protection, and the rules backing it, have changed over the course of the game’s history.

Contents

• 1 Description
• 2 History
• 3 Rules
  • 3.1 Variants
• 4 Examples
• 5 References
• 6 External links

Description[]

This ability represents a magical resistance to certain types of magic, often a specific color.^[3] It was introduced in Alpha and saw frequent use through Magic Origins. Protection was previously dropped from evergreen status to deciduous status but as of 2021 is officialy back to evergreen status. It’s an ability primary in white that can show up in other colors, usually with protection from something the color dislikes (an enemy color, artifacts for green, etc.).^[4]

Protection is commonly misunderstood as complete exemption from permanents, and effects created by cards, with the specified quality. However, protection is defined by a relatively narrow set of rules, which are often communicated using the mnemonic acronym DEBT. The permanent or player with protection cannot be:

• Damaged by sources with the specified quality. (All such damage is prevented.)
• Enchanted, equipped, or fortified by permanents with the specified quality.
• Blocked by creatures with the specified quality.
• Targeted by spells with the specified quality, or by abilities from sources of that quality.

The current (as of Core Set 2020) reminder text for protection largely reflects this, reading “This [object] can’t be blocked, targeted, dealt damage, enchanted, or equipped by anything [quality].”

History[]

Despite intuitive expectations for the keyword, protection was recognized as potentially complicated even prior to the game’s release. Early attempts to define protection led the Alpha designers to invent the fundamental concept of targeting.^[5] However, even the original rulebook described it informally, offering only examples of things that protection would prevent. ^[6]

A creature with protection from one or more colors of magic cannot be affected by any magic of those colors. For example, a creature with protection from blue cannot be blocked by blue creatures, dealt damage by blue creatures, or enchanted, damaged, or otherwise affected by blue cards. Damage done by such a creature cannot be prevented using blue cards. Note that the creature does not have this ability until it is successfully summoned. If, for example, you are summoning a creature with protection from blue magic, your rival can still cast a blue interrupt that affects the summoning spell.

Protection was excluded from core sets beginning with Sixth Edition and returned to them in Ninth Edition, reflecting concerns about its complexity for newer players. With the release of Magic Origins, protection was demoted from evergreen to deciduous, relegating it to only occasional use.^[7][8] In the three blocks following that decision, it was used only once: on Emrakul, the Promised End.

Later, it reappeared in Modern Horizons.^[9] It also returned in Core Set 2020, where it was back to evergreen on a probationary status.^[2][10][11] Although it doesn’t show up in every set, protection became officially evergreen again in 2021.^[12][13]

Two white cards have a condensed version of Protection: Sungold Sentinel and Skrelv, Defector Mite. Both have an activated ability that grants hexproof from a color and prevent blocking by creatures of that color, making up about half of protection’s text and most of its gameplay. As with many gameplay design choices, the “prevent damage” aspect is left out as to avoid the “infinite blocking” scenario.

Rules[]

From the glossary of the Comprehensive Rules (June 16, 2023—The Lord of the Rings: Tales of Middle-earth)

Protection

A keyword ability that provides a range of benefits against objects with a specific quality. See rule 702.16, “Protection.”

From the Comprehensive Rules (June 16, 2023—The Lord of the Rings: Tales of Middle-earth)

• 702.16. Protection
  • 702.16a Protection is a static ability, written “Protection from [quality].” This quality is usually a color (as in “protection from black”) but can be any characteristic value or information. If the quality happens to be a card name, it is treated as such only if the protection ability specifies that the quality is a name. If the quality is a card type, subtype, or supertype, the ability applies to sources that are permanents with that card type, subtype, or supertype and to any sources not on the battlefield that are of that card type, subtype, or supertype. This is an exception to rule 109.2.
  • 702.16b A permanent or player with protection can’t be targeted by spells with the stated quality and can’t be targeted by abilities from a source with the stated quality.
  • 702.16c A permanent or player with protection can’t be enchanted by Auras that have the stated quality. Such Auras attached to the permanent or player with protection will be put into their owners’ graveyards as a state-based action. (See rule 704, “State-Based Actions.”)
  • 702.16d A permanent with protection can’t be equipped by Equipment that have the stated quality or fortified by Fortifications that have the stated quality. Such Equipment or Fortifications become unattached from that permanent as a state-based action, but remain on the battlefield. (See rule 704, “State-Based Actions.”)
  • 702.16e Any damage that would be dealt by sources that have the stated quality to a permanent or player with protection is prevented.
  • 702.16f Attacking creatures with protection can’t be blocked by creatures that have the stated quality.
  • 702.16g “Protection from [quality A] and from [quality B]” is shorthand for “protection from [quality A]” and “protection from [quality B]”; it behaves as two separate protection abilities. If an effect causes an object with such an ability to lose protection from [quality A], for example, that object would still have protection from [quality B].
  • 702.16h “Protection from all [characteristic]” is shorthand for “protection from [quality A],” “protection from [quality B],” and so on for each possible quality the listed characteristic could have; it behaves as multiple separate protection abilities. If an effect causes an object with such an ability to lose protection from [quality A], for example, that object would still have protection from [quality B], [quality C], and so on.
  • 702.16i “Protection from each [set of characteristics, qualities, or players]” is shorthand for “protection from [A],” “protection from [B],” and so on for each characteristic, quality, or player in the set. It behaves as multiple separate protection abilities.
  • 702.16j “Protection from everything” is a variant of the protection ability. A permanent or player with protection from everything has protection from each object regardless of that object’s characteristic values. Such a permanent or player can’t be targeted by spells or abilities and can’t be enchanted by Auras. Such a permanent can’t be equipped by Equipment, fortified by Fortifications, or blocked by creatures. All damage that would be dealt to such a permanent or player is prevented.
  • 702.16k “Protection from [a player]” is a variant of the protection ability. A permanent or player with protection from a specific player has protection from each object that player controls and protection from each object that player owns not controlled by another player, regardless of that object’s characteristic values. Such a permanent or player can’t be targeted by spells or abilities the specified player controls and can’t be enchanted by Auras that player controls. Such a permanent can’t be equipped by Equipment that player controls, fortified by Fortifications that player controls, or blocked by creatures that player controls. All damage that would be dealt to such a permanent or player by sources controlled by the specified player or owned by that player but not controlled by another player is prevented.
  • 702.16m Multiple instances of protection from the same quality on the same permanent or player are redundant.
  • 702.16n Some Auras both give the enchanted creature protection from a quality and say “this effect doesn’t remove” either that specific Aura or all Auras. This means that the specified Auras aren’t put into their owners’ graveyards as a state-based action. If the creature has other instances of protection from the same quality, those instances affect Auras as normal.
  • 702.16p One Aura (Benevolent Blessing) gives the enchanted creature protection from a quality and says the effect doesn’t remove certain permanents that are “already attached to” that creature. This means that, when the protection effect starts to apply, any objects with the stated quality that are already attached to that creature (including the Aura giving that creature protection) will not be put into their owners’ graveyards as a state-based action. Other permanents with the stated quality can’t become attached to the creature. If the creature has other instances of protection from the same quality, those instances affect attached permanents as normal.

Variants[]

Protection is written in the form “protection from…”, followed by one or more qualities or characteristics. The first examples of protection are from colors, but many other variants have been printed.

Last Updated for Core Set 2021

1. ↑ ^{a b} Tsabo Tavoc originally had “protection from Legends”, but this was errataed to “protection from legendary creatures” when “Legend” ceased to be a creature subtype.

Examples[]

Example

White Knight
Creature — Human Knight
2/2
First strike (This creature deals combat damage before creatures without first strike.)
Protection from black (This creature can’t be blocked, targeted, dealt damage, or enchanted by anything black.)

References[]

1. ↑ Mark Rosewater (March 28, 2022). “Deciduous”. magicthegathering.com. Wizards of the Coast.
2. ↑ ^{a b} Mark Rosewater (June 18, 2019). “Did R&D change their mind on protection being removed from evergreen?”. Blogatog. Tumblr.
3. ↑ Mark Rosewater (May 29, 2019). “If a creature has protection from a color will that protection prevent effects such as Infest?”. Blogatog. Tumblr.
4. ↑ Mark Rosewater (June 5, 2017). “Mechanical Color Pie 2017”. magicthegathering.com. Wizards of the Coast.
5. ↑ Brady Dommermuth (June 01, 2009). “Mechanically Inclined”. magicthegathering.com. Wizards of the Coast.
6. ↑ John Carter (December 25, 2004). “The Original Magic Rulebook”. magicthegathering.com. Wizards of the Coast.
7. ↑ Mark Rosewater (June 8, 2015). “Evergreen Eggs & Ham”. magicthegathering.com. Wizards of the Coast.
8. ↑ Mark Rosewater (August 06, 2017). “I noticed that there have been very few cards with “Protection” in recent sets.”. Blogatog. Tumblr.
9. ↑ Matt Tabak (May 31, 2019). “Modern Horizons Mechanics”. magicthegathering.com. Wizards of the Coast.
10. ↑ Mark Rosewater (June 18, 2019). “Protection is back? i mean, i love that, but how come?”. Blogatog. Tumblr.
11. ↑ Mark Rosewater (June 24, 2019). “Core Than Meets The Eye”. magicthegathering.com. Wizards of the Coast.
12. ↑ Mark Rosewater (October 18, 2021). “Mechanical Color Pie 2021 Changes”. magicthegathering.com. Wizards of the Coast.
13. ↑ Mark Rosewater (March 28, 2022). “Deciduous”. magicthegathering.com. Wizards of the Coast.

External links[]

• A Planeswalker’s Primer for Magic 2011: Protection (Video). Magic: The Gathering. YouTube.

Community content is available under CC BY-NC-SA 2.5 unless otherwise noted.

• Fantasy

Three rules for data protection | Evernote

Privacy Center – PrivacyRegional Information – California – EU General Data Protection Regulation (GDPR) – Brazil – More InformationThree Data Protection RulesPrivacy Notice for Job SeekersMore Privacy Information – Cookie Information – Disclosure Report – Suppliers Services – Privacy Center Updates – Legal Help Home – Terms

• Privacy Center

• Information for specific regions

• Three Data Protection Rules

• Job Seeker Privacy Notice

• Additional privacy information

3 DATA PROTECTION RULES EVERNOTE

• Your information belongs only to you

• Your data is protected

  All information you post to Evernote is private by default. We do not specialize in “big data” and do not try to make money from your information. Our systems automatically analyze your data to enable Evernote features, such as finding and showing related notes, and to bring you information about important features and products that we think can make your Evernote experience better. We never share or sell your data to third parties for advertising purposes.

  Our business model is old fashioned: we only make money if you choose to pay for our great product. This means that trust is our main asset, and maintaining the confidentiality of your data is a fundamental principle of our work.

  Evernote allows you to post and share notes with other people. These are additional features and only you decide whether to use them or not. If you choose to link your Evernote account to one of our partner services, the partner may have access to all or part of your data. When you connect, we’ll let you know what the partner app is accessing in your account, and you can disable it at any time.

  In addition, we have put in place measures to prevent accidental data loss or theft. Everything you put into Evernote is synced and stored in a secure data center with multiple redundant servers, drives, and backup systems physically located elsewhere. Data between Evernote users and servers (and various data centers) is encrypted. Proven technologies such as two-factor authentication are available to all users, and we are constantly looking for ways to improve data protection. We take great care to protect your password, and no one on the Evernote team will ever ask you for it.

  We support the industry’s efforts to promote full transparency regarding data requests from government agencies, and have established a comprehensive legal process for such requests. For more information, see our Transparency Report.

• Your data is portable

Managing branch protection rule – GitHub Documentation

You can create a branch protection rule to enforce certain workflows on one or more branches, such as requesting a review for approval or passing status checks on all pull requests that are merged into a protected branch.

Protected branches are available in public repositories when using GitHub Free and GitHub Free for organizations, and in public and private repositories when using GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub Products.

For a specific branch, all branches, or any branch that matches the name pattern specified using the fnmatch syntax, you can create a branch protection rule in the repository. For example, to protect all branches that contain the word release , you could create a branch rule for *release* .

You can create a rule for all current and future branches in a repository using the wildcard syntax * . Since GitHub uses File::FNM_PATHNAME syntax flag File.fnmatch , * wildcard does not match directory separators ( / ). For example, will match all branches qa/* starting with qa/ and containing a single slash, but will not match qa/foo/bar . You can include any number of slashes after qa with qa/**/* which will match, for example . qa/foo/bar/foobar/hello-world You can also extend the qa string with qa**/**/* using to make the rule more inclusive.

See the fnmatch documentation for more information on syntax options.

If a repository has multiple branch protection rules that refer to the same branches, the rules that specify a specific branch name have the highest priority. If a particular branch name is specified in multiple branch protection rules, the rule created first will have the highest priority.

Branch protection rules that use a special character, such as * , ? or ] are applied in the order they were created, so older rules with those characters take precedence.

To create an exception to an existing branch protection rule, you can create a new rule with a higher priority, such as a rule for a specific branch name.

For more information about each of the available branch protection options, see About Protected Branches.

Note: Only one branch protection rule can be applied at a time. This means that it can be difficult to know which rule will apply if multiple versions of a rule target the same branch. For an alternative to branch protection rules, see About Rule Sets.

When you create a branch protection rule, it is not necessary that the specified branch already exists in the repository.

1. On GitHub.com, go to the main page of the repository.

2. Under the repository name, click Options . If the Options tab is not visible, select the drop-down menu and click the Options button.

3. In the Code and Automation section of the sidebar, click Branches .

4. Next to Branch Protection Rules, click Add Rule.

5. In the Branch Name Template section, enter the name of the branch or template that you want to protect.

6. Optionally enable required pull requests.

   Note: If you select Close old pull request approvals when pushing new commits and (or ) Require approval of the latest checked push option, manually creating a pull request merge commit and pushing it directly to the protected branch will fail, if the content of the merge does not exactly match the merge generated by GitHub for the pull request.

   In addition, when using these options, the review approval will be rejected as stale if the merge base makes new changes after the review is submitted. A merge base is a commit that is the last common ancestor between a topic branch and the base branch. If the merge base changes, the pull request cannot be merged until someone approves the work again.

   • Under “Protect relevant branches”, select Require a pull request before merging .

   • Optionally, to require approval before merging the pull request, select Require approval .

     Select the Required number of approvals before merge drop-down menu, and then select the number of approval checks you want to require on the branch.

   • Optionally, to skip pull request approval when pushing a code change commit to a branch, select option Ignore obsolete pull request assertions when submitting new commits .

   • If you want to require code owner review if the pull request affects code with an assigned owner, select option Require code owner review . For more information, see About code owners.

   • Optionally, to allow certain actors to push code to a branch without creating pull requests when required, select Allow certain subjects to skip creating pull requests . Then, find and select the actors you want to be allowed to skip creating a pull request.

   • If the repository is part of an organization, optionally select the option Restrict ability to skip pull request checks . Then, in the search box, find and select the actors that are allowed to deny pull request checks. For more information, see Rejecting Pull Request Validation.

   • Optionally, to require anyone other than the last one to submit to a branch to approve a pull request before merging, select Require last checked submission approval. For more information, see About Protected Branches.

7. Enable mandatory status checks if necessary. For more information, see About status checks.

   • Select option Require status checks before merging .
   • To ensure that pull requests are tested with the latest code in the protected branch, select the option Require branches up to date before merging .
   • In the search box, search for status checks by selecting the checks you need.

8. If necessary, select option Require contention before merging .

9. If necessary, select the option Require signing of commits .

10. If necessary, select parameter Require linear history .

11. If you want to merge pull requests using a merge queue, select the option Require use of merge queue . For more information about merge queues, see Managing the Merge Queue.

    Tip: The pull request merge queue feature is currently in public beta and is subject to change.

12. If you want to select the environments to which changes must be successfully deployed before merging, select the Require successful deployment before merging option, and then select the environments.

13. Make the branch read-only if necessary.

    • Select Lock branch .
    • If necessary, select Enable fork synchronization to enable fork synchronization.

14. If necessary, select Do not allow bypassing the above parameters .

15. Optionally enable branch restrictions on public repositories owned by a GitHub Free organization and all repositories owned by an organization using GitHub Team or GitHub Enterprise Cloud.

    • Select the option Restrict users who can push to the respective branches .
    • Optionally, to also restrict the creation of corresponding branches, select Restrict submissions that create corresponding branches .
    • In the search box, search for and select the people, teams, or applications that will have permission to push a protected branch or create a corresponding branch.

16. Optionally, in the “Rules that apply to everyone, including administrators” section, select the option Allow push .

    Then choose who can push to the branch.

    • Select All to allow anyone with at least write permissions to the repository, including administrators, to push to the branch.

    • Select Specify who can push to allow only certain principals to push to the branch. Then find and select those subjects.

      For more information about pushing, see About Protected Branches.

17. If necessary, select parameter Allow deletion .

18. Click the button Create .

1. On GitHub.com, go to the main page of the repository.

2. Under the repository name, click Options . If the Options tab is not visible, select the drop-down menu and click the Options button.

3. In the Code and Automation section of the sidebar, click Branches .