anchor.diff:  Git - g3 : poll for new changes disabled with no blacklisting.
   Git - g4 : poll for new changes enabled with no blacklisting.
   
  -    <img src="/assets/images/blog/cd-hacks/material-blacklisting.jpeg" alt="Blacklisting Materials in GoCD"/>
  +<img src="/assets/images/blog/cd-hacks/material-blacklisting.jpeg" alt="Blacklisting Materials in GoCD"/>
       
   Here’s a breakdown of how your pipeline behaves when there are commits made to the source code materials. 
   
  
positive.code: title: How to Work with Materials in GoCD
  type: post
  author: Ankit Srivastava
  excerpt: "In this post, we'll look at environment strategy including artifact promotion and leveraging modern infrastructure for dynamic environments."
  summary_image: "/assets/images/blog/cd-hacks/cd-hacks-gocd-materials.jpg"
  title_tag_of_header: "How to Works with Materials in GoCD | GoCD Blog"
  meta_description: "You can start with thinking about what environments need to be created upfront and talking about the intended use cases for these environments. Different groups in your organization will have different competing needs. Your environment plan should accommodate the needs from different parties."
  meta_keywords: "Microservices, continuous delivery, microservice environment, environment strategy, artifacts, provision environment"
  tags: CD Hacks
  ---
  <% content_for :banner do %>
  
negative.code: 
  In order to perform whitelisting, you choose “Invert the file filter, e.g. a blacklist becomes a whitelist instead.” option as shown below.
  
  <img src="/assets/images/blog/cd-hacks/edit_material_whitelist.png" alt="GoCD Fetch Materials"/>
  
  ##Server-side Material Blacklisting vs Fetch Materials
  
  