Urgent.News

What's breaking now, across thousands of outlets.

Tech

Git Branch Naming Conventions: Patterns and a CI Check

Originally published on DevToolHub . The git branch naming conventions I would use are a lowercase type/short-description pattern, such as fix/empty-password-crash , with an optional ticket number. Git enforces only a short list of hard rules, so the useful part is checking the rest automatically. I tested on Git 2.56.0 and gh 2.103.3, including a CI check that passed and failed on real pull…

When creating Git branch names, follow a lowercase type/short-description pattern with an optional ticket number. Git permits uppercase letters and certain special characters, but prefix schemes help avoid conflicts. Use lowercase letters to prevent naming clashes on case-sensitive file systems. A CI check can automatically verify the branch name format, passing for valid names and failing for invalid ones.

For example, the branch name "feat/4-empty-password-crash" was created for issue #4, while "Fix_Login-Bug" was rejected by the CI check. The branch name format must match the pattern: one of feat, fix, docs, or chore followed by a short description with lowercase letters and numbers. This naming convention helps maintain a consistent and easily identifiable branching structure within the Git repository.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The Agents Are Capable Enough — This Week's Research Is About Catching How They Fail

This edition of the AI Agents Digest covers what's new for agent builders between 2026-11-10 and 2026-11-17: a dense week of security audits, failure-mode benchmarks, memory research, and…

  • Researchers identify risky fallback patterns violating safety boundaries
  • New architectures separate reasoning from execution
  • Multi-LLM agentic AI optimized for edge computing

Secure Your APIs: OAuth2 and JWT for Beginners

Repository with the companion code for the tutorial APIs are frequent targets for bad actors since they expose data and functionality.

  • OAuth 2.0 handles authorization delegation, while JWT provides secure token format
  • JWT includes identity info and acts as authorization ID once issued
  • OAuth2 and JWT complement each other in a system with four key roles

Amazon’s Black Friday ‘Deals’ Were Mostly Decoys – What That Means for Cloud Engineers

1. What was released / announced Groundwork Collaborative’s investigation (see the link above) revealed that nearly 1 in 3 Amazon Black Friday and Cyber Monday deals advertised on the retail site…

  • 33% of Amazon's Black Friday/Cyber Monday deals were not actual savings
  • Nearly 10% of advertised discounts were price increases
  • Impacts budget forecasting, security/compliance, and automation pipelines for cloud engineers

More from Tuesday 17 November →