Boilerplate repository configuration (#1)

* Remove boilerplate notice from LICENSE file

* Update README.md to enhance project description and formatting

* Add CODEOWNERS file to define repository ownership

* Add dependabot configuration for automated dependency updates

Author: rdhar

.github/CODEOWNERS

@@ -0,0 +1,6 @@
+# Each line is a file pattern followed by one or more owners.
+# Order is important as the last matching pair takes precedence.
+# https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
+
+# Default
+* @rdhar

.github/dependabot.yml

@@ -0,0 +1,21 @@
+---
+version: 2
+
+updates:
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: daily
+    groups:
+      cicd:
+        patterns:
+          - "*"
+
+  - package-ecosystem: bun
+    directory: /
+    schedule:
+      interval: daily
+    groups:
+      bun:
+        patterns:
+          - "*"

LICENSE

@@ -175,18 +175,7 @@
 
    END OF TERMS AND CONDITIONS
 
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
+   Copyright 2016-present Rishav Dhar
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

README.md

@@ -1,2 +1,3 @@
-# HotFix.Day
-Things break in production; we write about why. Incident analysis, infrastructure automation, CI/CD, observability, and open-source SRE tooling.
+# HotFix.Day — Fixes, Failures & the Future of DevOps
+
+> Things break in production; we write about why. Incident analysis, infrastructure automation, CI/CD, observability, and open-source SRE tooling.