2. Lock down all GitHub repo settings and don’t let teams add the CI settings back.
3. Make sure CI job enablement and changed go thorough the rigorous approval process.
4. PROFIT
2. Lock down all GitHub repo settings and don’t let teams add the CI settings back.
3. Make sure CI job enablement and changed go thorough the rigorous approval process.
4. PROFIT
2. Make it inconsistent with industry adopted standards and practices.
3. Sabotage or delay linters and automated checks.
4. PROFIT
2. Make it inconsistent with industry adopted standards and practices.
3. Sabotage or delay linters and automated checks.
4. PROFIT
2. Append to them
3. PROFIT
2. Append to them
3. PROFIT
Change requirements as far into development as possible. To avoid blame, obfuscate requirements from the start.
Change requirements as far into development as possible. To avoid blame, obfuscate requirements from the start.