Add guidelines

CHANGELOG.md

@@ -2,6 +2,13 @@
 
 All notable changes to this project will be documented in this file.
 
+## [UNRELEASED]
+
+### Added
+
+- Code of Conduct (CoC).
+- Contributing Guidelines.
+
 ## [0.2.1] - 2026-03-31
 
 ### Added

CODE_OF_CONDUCT.md

@@ -0,0 +1,71 @@
+# Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [thedevmystic@gmail.com](mailto:thedevmystic@gmail.com).
+All complaints will be reviewed and investigated and will result in a response 
+that is deemed necessary and appropriate to the circumstances. The project team
+is obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

CONTRIBUTING.md

@@ -0,0 +1,62 @@
+# Contributing to thedevmystic/github-actions!
+
+First off, thank you for considering contributing to github-actions! It's people
+like you who make the open-source community a great place!
+
+To maintain a high quality of code and a friendly environment, please take a
+moment to review these guidelines.
+
+## Code of Conduct
+
+By participating in this project, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md).
+Please be respectful and professional in all interactions.
+
+## How to Contribute
+
+### Reporting Bugs
+
+* **Check the Issue Tracker:** Before opening a new issue, please search to see
+  if the bug has already been reported.
+* **Be Specific:** Use a clear title and provide as much context as possible
+  (OS, version, steps to reproduce). Use the bug report template to get started.
+* **Provide Logs:** If applicable, include error messages or screenshots.
+
+### Suggesting Enhancements
+
+* **Explain the 'Why':** Describe the problem this enhancement solves. Use
+  feature request template to get started.
+* **Scope:** Keep suggestions focused. Large-scale changes may need a formal
+  RFC (Request for Comments).
+
+### Pull Requests (PRs)
+
+1. **Fork the repo** and create your branch from `main`.
+2. **Write clean code:** Follow the existing style and naming conventions.
+3. **Add tests:** New code = New tests! If you're adding a feature, please
+   include tests to ensure it stays working.
+4. **Pass worflows:** Ensure it passes all necessary tests (such as pre-commit linting).
+5. **Update documentation:** If your change affects how the project is used,
+   update the README or docs.
+6. **Submit the PR:** Link it to any relevant issues and provide a clear
+   description of your changes.
+
+## Development Setup
+
+To get started with the codebase locally:
+
+1. Clone your fork: `git clone https://github.com/thedevmystic/github-actions.git`
+2. Enter the directory: `cd github-actions`
+
+## Testing
+
+Run the test suite to ensure everything is functioning correctly:
+
+* Go to GitHub Actions Tab
+* Run the specific action
+
+## Communication
+
+If you have questions or want to discuss ideas before coding, feel free to:
+
+* Open a **Discussion** on GitHub.
+* Join our [Discord](https://discord.gg/JxJMzshA) channel.