Search
Results for “change-management”
- software-engineering
GitHub Changelog Triage: A Weekly Workflow for Releases, Improvements, and Retirements
Turn GitHub product changes into a 30-minute weekly operating process. Learn how to subscribe, classify releases, improvements, and retirements, assign accountable owners, run proportionate tests, and preserve decisions in a searchable log.
- developer-tools
A Practical Workflow for Monitoring GitHub Platform and Copilot Changes Without Reading Every Changelog
Use the GitHub Changelog as your source of record and a release-notes aggregator as an early-warning layer. This workflow shows how to triage Copilot, Actions, security, CLI, and Enterprise updates into ignore, review, test, or act-now decisions.
- software-engineering
GitHub Copilot Agent Mode vs Copilot Edits in VS Code: A Task-Selection Workflow for Safer Changes
Use Copilot Edits for bounded changes you can specify and review file by file. Use agent-oriented workflows when a task requires discovery, implementation, testing, and iteration—and add explicit checkpoints before generated changes reach a branch.
- software-engineering
9-Step Rollback-Ready Release Checklist for Small Engineering Teams
Turn release management into a repeatable, executable checklist with test evidence, named approvers, deployment ownership, measurable rollback triggers, and post-release verification.
- software-engineering
A Practical Jenkins Hardening Runbook: Reduce Plugin Risk and Remove Internet Exposure
Use this remediation runbook to inventory Jenkins plugins, prioritize updates by reachable risk, remove unnecessary public exposure, restrict administration, and prove the server is safer after each change.
- software-engineering
GitHub Releases vs Tags: A Repeatable gh CLI Release Workflow
A Git tag can point to the right commit while a GitHub Release still points users at the wrong package. Learn the practical difference, then use gh CLI and Git commands to create, inspect, and verify a release with a checklist your team can repeat.
- productivity
Build a Faster Technical Knowledge Feed With AI Curation, Tags, and Weekly Reviews
Turn an AI-driven news feed into a practical technical reading system. This workflow shows how to filter articles, save only reusable ideas, tag them consistently, and convert a week of reading into decisions and experiments.
- security
GHES After CVE-2026-3854: An Environment-Focused RCE Response Checklist
CVE-2026-3854 was reported as an X-Stat push-option injection vulnerability affecting GitHub Enterprise Server. Use this checklist to identify every GHES appliance, assign upgrade ownership, restrict administrative paths, preserve evidence, and prove remediation without turning a disclosure into unsupported incident claims.
- software-engineering
A Pre-Launch GenAI Risk Checklist for Internal Chatbots and Developer Tools
Turn NIST’s generative AI risk guidance into a practical release gate for a coding assistant, repository chatbot, or internal support bot. Use this checklist to test data exposure, harmful outputs, human review, evaluation coverage, and incident response before enabling real users.
- software-engineering
A Practical Scorecard for Measuring Open-Source Dependency Reuse
As dependency reuse grows, a package list is not enough. This engineering scorecard turns inventory, update cadence, provenance review, and abandoned-package exposure into measurable controls that teams can use in planning and release reviews.
- software-engineering
GitHub Releases vs Tags: A Practical Checklist for Shipping Downloadable Software
A Git tag identifies a commit; a GitHub release turns that point in history into a downloadable, documented software delivery. Use this repeatable checklist to create release notes, attach verifiable assets, protect the release boundary, and inspect published releases with gh release view.
- security
CodeQL 2.26.4 Upgrade Checklist for Go, Rust, and GitHub Actions Repositories in 2026
CodeQL 2.26.4 adds Go 1.27 support, improves Rust alert locations, and broadens GitHub Actions security detection accuracy. Use this playbook to identify affected repositories, establish a baseline, rerun scans, and review changed results without treating every location change as a new vulnerability.
- technology
Migrate download-artifact to v4: Test Paths, Compatibility, and Deploy Contracts
A practical before-and-after migration for GitHub Actions artifact workflows. Learn how v4 changes artifact compatibility, availability, and download directories—and add checks that catch broken deploy paths before production.
- software-engineering
A Pull-Request-Ready GitHub Actions CI/CD Security Checklist
Use this five-minute GitHub Actions review checklist to block unsafe permissions, secret exposure, third-party action drift, untrusted artifacts, and missing audit signals before a workflow change merges.
- software-engineering
GitHub Releases vs Actions Artifacts: A CI Delivery Pipeline That Keeps Test Outputs Temporary
Use GitHub Actions artifacts for short-lived CI evidence and job-to-job handoffs, then publish only scanned, approved distributables as GitHub Release assets. This worked pipeline shows where the boundary belongs, how retention changes the decision, and how to enforce it.
- software-engineering
Diagnose Node.js Event Loop Latency: Blocked Code, CPU Saturation, or Downstream I/O
Use Node.js event-loop delay and utilization metrics as an incident decision system. This guide shows what to measure first, how to distinguish synchronous blocking from CPU saturation and downstream I/O pressure, and when code changes are actually justified.
- software-engineering
A Practical Checklist for Publishing Tamper-Resistant GitHub Releases with Immutable Tags and Assets
Separate temporary CI artifacts from the files users download, then publish a GitHub release whose assets and associated Git tag cannot be changed afterward. This checklist covers build promotion, checksums, release workflows, and the operational tradeoffs of immutability.
- software-engineering
Migrate download-artifact v3 to v4 and Verify Deploy Directory Layouts
A practical GitHub Actions migration guide for replacing actions/download-artifact@v3 with v4 without silently changing what your deploy job publishes. Map common download patterns, update artifact producers, and add layout checks to a build-test-deploy pipeline.
- developer-tools
Spring Tools 5.2 Embedded MCP Server: A Safe Workflow Guide for Claude Code and Spring Project Context
Spring Tools 5.2 introduces an experimental Claude Code plugin and embedded MCP server, but safe use depends more on workspace isolation than on prompts. This workflow shows a minimal validation change, test contract, secret-safe project preparation, and rollback procedure.