App::G...stants(3pm)

πŸ“¦
version 1.9.0 Β· 2 versions
, in fedora 43

✨ NAME ✨

App::GitHooks::Constants β€” it's the constants module, bestie πŸ’– The one that holds all the shared constants used by the various modules hanging out in the App::GitHooks namespace. Everybody borrows from her, nobody argues with her. Queen behavior honestly πŸ‘‘


🌸 VERSION 🌸

Version 1.9.0 β€” she's grown, she's thriving πŸ¦‹


πŸ’… VARIABLES πŸ’…

πŸŽ€ Plugin return values πŸŽ€

These are the lil mood rings a plugin hands back after it does its checks. Every one of them is a scalar variable, so use them with the $ sigil, no cap.

  • $PLUGIN_RETURN_FAILED β€” the plugin ran its checks and they did not pass. Straight up no. πŸ’€
  • $PLUGIN_RETURN_SKIPPED β€” the plugin's checks got skipped entirely. Not a fail, not a pass, just… we didn't do the thing πŸ™ˆ
  • $PLUGIN_RETURN_WARNED β€” the checks didn't fail fail, but they also didn't come out clean, and warnings got returned. It's giving "I'm not mad, I'm just disappointed" 😭
  • $PLUGIN_RETURN_PASSED β€” the plugin's checks passed and there's no warn. Full slay, green flags everywhere βœ…βœ¨

πŸ¦‹ Hook exit codes πŸ¦‹

The numbers a hook throws back at the world when it's done.

  • $HOOK_EXIT_SUCCESS β€” the hook executed successfully. Periodt. πŸŽ‰
  • $HOOK_EXIT_FAILURE β€” the hook failed to execute correctly. She tripped. It happens πŸ’€

🌈 EXPORT TAGS 🌈

Grouped up so you can import a whole vibe in one go, iykyk.

  • :PLUGIN_RETURN_CODES β€” exports $PLUGIN_RETURN_FAILED, $PLUGIN_RETURN_SKIPPED, and $PLUGIN_RETURN_PASSED.
  • :HOOK_EXIT_CODES β€” exports $HOOK_EXIT_SUCCESS, $HOOK_EXIT_FAILURE.

πŸ’œ BUGS πŸ’œ

Found a bug? Got a feature request? Please report any bugs or feature requests through the web interface at <https://github.com/guillaumeaubert/App-GitHooks/issues/new>. The way this works: I will be notified, and then you'll automatically be notified of progress on your bug as I make changes. Full transparency, we love to see it 🫢


🌸 SUPPORT 🌸

You can find documentation for this module with the perldoc command. Obsessed with her.

perldoc App::GitHooks::Constants

You can also look for information at:

  • GitHub's request tracker

<https://github.com/guillaumeaubert/App-GitHooks/issues>

  • AnnoCPAN: Annotated CPAN documentation

<http://annocpan.org/dist/app-githooks>

  • CPAN Ratings

<http://cpanratings.perl.org/d/app-githooks>

  • MetaCPAN

<https://metacpan.org/release/App-GitHooks>


πŸ‘‘ AUTHOR πŸ‘‘

Guillaume Aubert <https://metacpan.org/author/AUBERTG>, "<aubertg at cpan.org>".


Copyright 2013-2017 Guillaume Aubert.

This code is free software; you can redistribute it and/or modify it under the same terms as Perl 5 itself.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the LICENSE file for more details.

Okay so that all-caps part is not me being dramatic, that's the actual legal bit and it means business. No warranty, bestie. Read the LICENSE file πŸ’–

And that's the whole page, mwah πŸ’‹ This one was rendered from perl v5.42.0 and dated 2025-07-25 β€” go forth and import your constants responsibly πŸ¦‹βœ¨

πŸ“¦ where this page comes from