2026-04-06T04:15:43Zhttps://yabu.meNostr notes by src/bin/readme.rssrc/bin/readme.rshttps://yabu.me/npub1f79atqxv09ajrl6z8sgfq2tvf0ufxxtva74c5dr5frfwac7u938su3arswhttps://avatars.githubusercontent.com/u/135379339?s=400&u=11cb72cccbc2b13252867099546074c50caef1ae&v=4https://avatars.githubusercontent.com/u/135379339?s=400&u=11cb72cccbc2b13252867099546074c50caef1ae&v=4https://yabu.me/nevent1qqsw22n3zlvknxcg6q3xer0gagrdt8nyzxvwd4mje4lxr06n5mc9etczyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7jveda3//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-03T02:22:23Zhttps://yabu.me/nevent1qqsr2kqsvkjnud5lyc657wy2kdenkrf85ukc0kjk40njjd5ujwqnalqzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7jnf2c7//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-03T02:17:31Zhttps://yabu.me/nevent1qqsyeg0j5kwxq7n79sqnadr2z3lnpe7ntx8g9xevuk2kgpuj34tqxzczyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky73zzup3//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-03T02:17:13Zhttps://yabu.me/nevent1qqsp4270tzuh4kyxefmfjh6ftzq73njt6mp3re8805726r8l9vrjyyszyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7vwy6zx//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-03T02:10:34Zhttps://yabu.me/nevent1qqswu53xtpjzukdnuyv0mqy9zaqzgr0s8feujhw2vdeljr5apwygetszyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7vjhtch//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-03T01:40:34Zhttps://yabu.me/nevent1qqswgxhqean9pdzwueslxdvduyku6wmjfp3wgkg6ejn2lzwka3v0ntqzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky725hha0//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-03T00:23:33Zhttps://yabu.me/nevent1qqsgtpdpe6r284yct70g88j0kp6czpra0vaer9x2xynj45jt2uef9cszyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7vg02qn//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-02T22:42:51Zhttps://yabu.me/nevent1qqszf85kc5zsghx7wxljy0vhnncgpjnq2z7e5hn0vqlrspv7wmsheqgzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7sadfye//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-02T22:35:30Zhttps://yabu.me/nevent1qqsfuxxzs32mzg4jffpserkf8trqf08m6mr7wzx6348cjeqnz7cw7xszyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7n7zffa//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-02T18:53:42Zhttps://yabu.me/nevent1qqsveej8aa7tuk4leqp6y4yc995xpevgrjth04e7hh65dgh3jm8d7hczyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky78997yh//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-02T18:52:52Zhttps://yabu.me/nevent1qqs00qnyj2g9d8qwwhry7jfnetx9gtdst0ycrzkz5ckzuvr23c2ukegzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7f45gg0//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-02T18:52:09Zhttps://yabu.me/nevent1qqspug459qac0h3my7pk0xqnj8f0gjj4nrprpf04kuzv2ms9934te0qzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7fruhy3//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-02T18:51:17Zhttps://yabu.me/nevent1qqsyszsxjmacu6waqtteudycvfpfcszhv9qkjlumkzzggdgv265tw9qzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7sl3667//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-02T00:28:39Zhttps://yabu.me/nevent1qqsdsvkq7xc3q0rtwxfklfcca9e8ejgzzf7wzp5pqskdkx7qk05vcyszyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7m70ptz//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-02T00:15:52Zhttps://yabu.me/nevent1qqsrxqer8cqg6hkuyua95wmfuf55e9phdyazqfgtkr47zgjednnfr3szyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky790ed59//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-02T00:08:23Zhttps://yabu.me/nevent1qqswy5dlzqkwdls5sfalntzezakld8jd83lgkcmlych0u7acpmlg6eszyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7u07424//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-02T00:07:14Zhttps://yabu.me/nevent1qqsqtlak7ffcznrjva25u785g2wc87k4a9psm5zr69e8d88auepwqzczyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7uqr4aw//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-02T00:05:09Zhttps://yabu.me/nevent1qqsgfm6dhuv8tkdd40nh5szjdt28ux7swq8mzqtjnt9af0td946mk3gzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky72gp99t//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-02T00:04:07Zhttps://yabu.me/nevent1qqsfxrz68jnej60fck87ekn92hc50ylkwevjqa8kkrsgpe50r335jpqzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky78hrsvu//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:57:21Zhttps://yabu.me/nevent1qqs9vjr7xjt6x9dvslp8jcale5xycju7jmkyl7663k0hgdygeqssdrgzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky72fxvjz//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:56:50Zhttps://yabu.me/nevent1qqs0w63jtpj4swkuvy89hxjprx3y8nnee7gmzvpj7ddfaksu389vhfszyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7k4rzps//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:52:30Zhttps://yabu.me/nevent1qqs2j5y4ezj393sveum2lsvtkuwrp5xfmhkmt05dqm5lr3fha3csg9szyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7pvkneu//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:50:20Zhttps://yabu.me/nevent1qqsw6cz96jtj5td9dm9rqk9uwem65tyafaak7pd72049vk9gcpqztyszyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7uwnud5//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:47:00Zhttps://yabu.me/nevent1qqsgnwca98ut9tjfvptrfx4cmzxmn86y3hc6gx682wlfpfdmvw0ns2czyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky75s7ejf//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:42:25Zhttps://yabu.me/nevent1qqstqxj659vcva53wgu3a7fafryhw89uz9zwhweaqwjgc25f99ws2zqzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7z3q3e3//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:39:05Zhttps://yabu.me/nevent1qqsgvgkh0mkje49h008e2kfxc2hkyw32vm4zhsmxcgy7pkq9jlc30cqzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7nhmp20//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:33:45Zhttps://yabu.me/nevent1qqsygx885apyqc32jfjymnsg8w37epxkuvaafusrldnm4j20dp6rztqzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7cuhh92//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:31:00Zhttps://yabu.me/nevent1qqsz0q8ha3q2ssw4s6u4ajcpwndtu24xxtu6nvu8rdsptdvwd82aw9gzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7vqc883//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:30:30Zhttps://yabu.me/nevent1qqs0zjtgfcul5xetm6sqkenwntdgmfg9rr9utv8s87rgq83qn39wvtczyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7uml3ys//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:29:11Zhttps://yabu.me/nevent1qqstrm7g5k7jemhv9pqj0qqd2e0ery8vppa90tmlqr60kwsckjtp0sczyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7lhlg72//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:26:57Zhttps://yabu.me/nevent1qqsyv9t5j5vpj3z0gggeemt439rlz7lxz50q0skpw0v6wv0gevrp5dszyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky73qhqy2//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:26:53Zhttps://yabu.me/nevent1qqsxsgzzxldz4wjzw7h60p5sv30v9ktnw4ej5jnnt03pq7k26j7z7hgzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky76xqyf0//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:19:56Zhttps://yabu.me/nevent1qqsqlmu33sksf895z6hch2y6fdnna58tx3qgxmt2l43hny6gz3l3t5gzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7g7q22y//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:13:20Zhttps://yabu.me/nevent1qqsdtx6yvcxej2fdx9nccx4wvunvnkcea3czgd02vn0wal0zggaanugzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7pz6vwq//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:12:27Zhttps://yabu.me/nevent1qqs9k9sz48cpc6gyfpuvycq227cytfmwrru7mvgtlhzhug9dzf6tylgzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7725k4u//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T23:09:28Zhttps://yabu.me/nevent1qqswqrk2526qekrxe5hgzuyelc9agz0jyv4hnkxmenfwhvgcv9y3gwszyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7v5e2jg//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T22:11:48Zhttps://yabu.me/nevent1qqsrjwpk2trvqfk8c35erhmmxq6xk6uvqzs9mepp2r43m87y5edxx0szyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7xmpwzf//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T22:02:18Zhttps://yabu.me/nevent1qqsvwgd99g3wt7nxv63ahd29v6ka4n47lhszvefvgla3plvw56zfqzqzyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7u80h8l//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T21:43:07Zhttps://yabu.me/nevent1qqsfqkqznqjmxfjrcmld0953hauymzt6gvq7j42wu5eyawag70ja24czyp8ch4vqe3uhkg0lgg7ppypfd39l3ycednh6hz35w3yd9mhrmsky7at2c6s//! A simple command-line tool that calculates and displays the ...
//! A simple command-line tool that calculates and displays the SHA-256 hash of<br/>//! its own source file.<br/>//!<br/>//! This utility demonstrates how to use the `get_file_hash!` macro to obtain<br/>//! the hash of a specified file at compile time and incorporate it into runtime<br/>//! logic.<br/>use get_file_hash::{BUILD_HASH, CARGO_TOML_HASH, LIB_HASH};<br/>use get_file_hash_core::get_file_hash;<br/>use sha2::{Digest, Sha256};<br/><br/>const README_TEMPLATE_PART0: &str = r##"# `get_file_hash` macro<br/><br/>This project provides a Rust procedural macro, `get_file_hash!`, designed to compute the SHA-256 hash of a specified file at compile time. This hash is then embedded directly into your compiled executable. This feature is invaluable for:<br/><br/>* **Integrity Verification:** Ensuring the deployed code hasn't been tampered with.<br/>* **Versioning:** Embedding a unique identifier linked to the exact source code version.<br/>* **Cache Busting:** Generating unique names for assets based on their content.<br/><br/>## Project Structure<br/><br/>* `get_file_hash_core`: A foundational crate containing the `get_file_hash!` macro definition.<br/>* `get_file_hash`: The main library crate that re-exports the macro.<br/>* `src/bin/get_file_hash.rs`: An example executable demonstrating the macro's usage by hashing its own source file and updating this `README.md`.<br/>* `build.rs`: A build script that also utilizes the `get_file_hash!` macro to hash `Cargo.toml` during the build process.<br/><br/>## Usage of `get_file_hash!` Macro<br/><br/>To use the `get_file_hash!` macro, ensure you have `get_file_hash` (or `get_file_hash_core` for direct usage) as a dependency in your `Cargo.toml`.<br/><br/>### Example<br/><br/>```rust<br/>use get_file_hash::get_file_hash;<br/>use get_file_hash::CARGO_TOML_HASH;<br/>use sha2::{Digest, Sha256};<br/><br/>fn main() {<br/> // The macro resolves the path relative to CARGO_MANIFEST_DIR<br/> let readme_hash = get_file_hash!("src/bin/readme.rs");<br/> let lib_hash = get_file_hash!("src/lib.rs");<br/> println!("The SHA-256 hash of src/lib.rs is: {}", lib_hash);<br/> println!("The SHA-256 hash of src/bin/readme.rs is: {}", readme_hash);<br/> println!("The SHA-256 hash of Cargo.toml is: {}", CARGO_TOML_HASH);<br/>}<br/>```<br/><br/>"##;<br/><br/>const README_TEMPLATE_PART1: &str = r"## Release<br/>## [`README.md`](./README.md)<br/><br/>```bash<br/>cargo run --bin readme > README.md<br/>```<br/><br/>## [`src/bin/readme.rs`](src/bin/readme.rs)<br/><br/>* **Target File:** `src/bin/readme.rs`<br/>";<br/><br/>const README_TEMPLATE_PART2: &str = r"##<br/><br/>## [`build.rs`](build.rs)<br/><br/>* **Target File:** `build.rs`<br/>";<br/><br/>const README_TEMPLATE_PART3: &str = r"##<br/><br/>## [`Cargo.toml`](Cargo.toml)<br/><br/>* **Target File:** `Cargo.toml`<br/>";<br/><br/>const README_TEMPLATE_PART4: &str = r"##<br/><br/>## [`src/lib.rs`](src/lib.rs)<br/><br/>* **Target File:** `src/lib.rs`<br/>";<br/><br/>const README_TEMPLATE_PART_NIP34: &str = r"## NIP-34 Integration: Git Repository Events on Nostr<br/><br/>This library provides a set of powerful macros and functions for integrating Git repository events with the Nostr protocol, adhering to the [NIP-34: Git Repositories on Nostr](<a href="https://github.com/nostr-protocol/nips/blob/master/34.md">https://github.com/nostr-protocol/nips/blob/master/34.md</a>) specification.<br/><br/>These tools allow you to publish various Git-related events to Nostr relays, enabling decentralized tracking and collaboration for your code repositories.<br/><br/>### Available NIP-34 Macros<br/><br/>Each macro provides a convenient way to publish specific NIP-34 event kinds:<br/><br/>* [`repository_announcement!`](#repository_announcement)<br/> * Publishes a `Repository Announcement` event (Kind 30617) to announce a new or updated Git repository.<br/>* [`publish_patch!`](#publish_patch)<br/> * Publishes a `Patch` event (Kind 1617) containing a Git patch (diff) for a specific commit.<br/>* [`publish_pull_request!`](#publish_pull_request)<br/> * Publishes a `Pull Request` event (Kind 1618) to propose changes and facilitate code review.<br/>* [`publish_pr_update!`](#publish_pr_update)<br/> * Publishes a `Pull Request Update` event (Kind 1619) to update an existing pull request.<br/>* [`publish_repository_state!`](#publish_repository_state)<br/> * Publishes a `Repository State` event (Kind 1620) to announce the current state of a branch (e.g., its latest commit).<br/>* [`publish_issue!`](#publish_issue)<br/> * Publishes an `Issue` event (Kind 1621) to report bugs, request features, or track tasks.<br/><br/>### Running NIP-34 Examples<br/><br/>To see these macros in action, navigate to the `examples/` directory and run each example individually with the `nostr` feature enabled:<br/><br/>```bash<br/>cargo run --example repository_announcement --features nostr<br/>cargo run --example publish_patch --features nostr<br/>cargo run --example publish_pull_request --features nostr<br/>cargo run --example publish_pr_update --features nostr<br/>cargo run --example publish_repository_state --features nostr<br/>cargo run --example publish_issue --features nostr<br/>```<br/><br/>";<br/><br/>/// The main entry point of the application.<br/>///<br/>/// This function calculates the SHA-256 hash of the `get_file_hash.rs` source<br/>/// file using a custom procedural macro and then prints the hash to the<br/>/// console. It also includes a basic integrity verification check.<br/>fn main() {<br/> // Calculate the SHA-256 hash of the current file (`readme.rs`) at<br/> // compile time. The `get_file_hash!` macro reads the file content and<br/> // computes its hash.<br/> let self_hash = get_file_hash!("readme.rs");<br/><br/> let status_message = if self_hash.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> let build_message = if BUILD_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let cargo_message = if CARGO_TOML_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/> let lib_message = if LIB_HASH.starts_with("e3b0") {<br/> "Warning: This hash represents an empty file."<br/> } else {<br/> "Integrity Verified."<br/> };<br/><br/> print!("{}{}{}", README_TEMPLATE_PART0, README_TEMPLATE_PART1, README_TEMPLATE_PART_NIP34);<br/> println!("* **SHA-256 Hash:** {}", self_hash);<br/> println!("* **Status:** {}.\n", status_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART2);<br/> println!("* **SHA-256 Hash:** {}", BUILD_HASH);<br/> println!("* **Status:** {}.\n", build_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART3);<br/> println!("* **SHA-256 Hash:** {}", CARGO_TOML_HASH);<br/> println!("* **Status:** {}.\n", cargo_message);<br/> //<br/> print!("{}", README_TEMPLATE_PART4);<br/> println!("* **SHA-256 Hash:** {}", LIB_HASH);<br/> println!("* **Status:** {}.\n", lib_message);<br/>}<br/>
2026-04-01T18:26:12Z