Signed in
We value your privacy
This site uses cookies to improve your browsing experience, analyze site traffic, and show personalized content.
Welcome to Pump.fun!
Pump lets anyone create coins, giving everyone equal access to buy and sell from the start. Prices can move quickly, so trade carefully.
By clicking this button, you agree to the Terms and Conditions, Privacy Policy, and certify that you are over 18 years old.
We value your privacy
This site uses cookies to improve your browsing experience, analyze site traffic, and show personalized content.
WARP: Warp Speed Protocol Commit Message ShortHand Framework # WARP, Warp Commit Speed Protocol WARP is a compact commit-message convention designed to keep commits clear, consistent, and traceable. Every commit message follows the same three-part structure: [TYPE][Scope][Description], where the type identifies the primary purpose, the scope identifies the main area affected, and the description briefly states what changed. ## Format Use: `[TYPE][Function/ClassName/ModuleName] [Scope][Description]` **TYPE** must be one of: * `FEAT` — New functionality * `IMPROVEMENT` — Improve existing functionality or performance * `BUG` — Fix incorrect or broken behavior * `SECURITY` — Security fixes, hardening, or vulnerability mitigation * `DOCS` — Documentation changes * `CLEANUP` — Remove useless, redundant, or obsolete code The type should describe the **primary purpose** of the commit. Do not introduce additional types. ## Scope `Scope` identifies the main area affected. Use a file, function, class, module, or feature name. Keep it short, specific, and use the actual name when practical. The scope should make it clear **where the change was made**, while the description explains **what changed**. Prefer the most specific relevant scope. Avoid vague scopes when a specific function, class, module, or feature can be named. If the change spans multiple unrelated areas, use `Multiple`. ## Description Write a short, action-oriented description of what changed. Keep it specific and avoid unnecessary explanation. Examples: `[FEAT][Authentication][Add OAuth login]` `[IMPROVEMENT][ImageProcessor][Optimize image resizing]` `[BUG][Navbar][Fix mobile alignment]` `[SECURITY][Authentication][Prevent token leakage]` `[DOCS][README.md][Update setup instructions]` `[CLEANUP][Utils][Remove unused helpers]` ## Rules Every commit should follow the same three-part structure. Choose exactly one of the six types, use the most relevant scope, and describe the change concisely. The type should represent the **primary purpose** of the commit. Do not combine multiple types in a single commit message. The scope should identify the **main area affected** and should be specific whenever practical. The description should clearly state **what changed** without unnecessary explanation. If a commit contains unrelated changes, split it when practical rather than making the message overly broad. The goal is simple: **what changed, where, and why it matters, in one line.** Source: https://github.com/kyegomez/WARP
