Add CONTRIBUTING.md (#488)

* Add templates for GitHub Issues

Add templates to be used when creating GitHub issues so that users know
what information is expected from them.

Signed-off-by: Tomáš Nevrlka <[email protected]>

* Add CONTRIBUTING.md

Contributors should know what is expected in their contributions. Add a
file that describes it.

Signed-off-by: Tomáš Nevrlka <[email protected]>

---------

Signed-off-by: Tomáš Nevrlka <[email protected]>

Author: tnevrlka

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,23 @@
+---
+name: Bug report
+title: ''
+labels: bug
+assignees: ''
+---
+
+## Problem Description
+Brief description of the issue
+
+## Steps to Reproduce
+1. Step one
+2. Step two
+3. Step three
+
+## Current Behavior
+What actually happens
+
+## Expected Behavior
+What should happen
+
+## Other information
+Logs, error messages, etc.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,18 @@
+---
+name: Feature request
+title: ''
+labels: enhancement
+assignees: ''
+---
+
+## Use Case
+Describe the problem or need this feature would address
+
+## Proposed Solution
+Your suggested implementation approach
+
+## Alternatives Considered
+Other potential solutions
+
+## Additional Context
+Any other relevant information

CONTRIBUTING.md

@@ -0,0 +1,70 @@
+# Contributing to build-service
+
+## Table of Contents
+
+* [Project Overview](#project-overview)
+* [How to Report Issues](#how-to-report-issues)
+* [How to Submit Pull Requests](#how-to-submit-pull-requests)
+  * [Development Workflow](#development-workflow)
+  * [Pull Request Guidelines](#pull-request-guidelines)
+  * [Security Best Practices](#security-best-practices)
+
+* [Review Process](#review-process)
+
+## Build service
+
+The build-service repository is used in [Konflux](https://konflux-ci.dev).
+Therefore, everybody should follow its [Code of Conduct](https://github.com/konflux-ci/community/blob/main/CODE_OF_CONDUCT.md).
+
+## How to Report Issues
+
+- We encourage early communication for all types of contributions.
+- Before filing an issue, make sure to check if it is not reported already.
+- If the contribution is non-trivial (straightforward bugfixes, typos, etc.), please open an issue to discuss your plans and get guidance from maintainers.
+- Please fill out included issue templates with all applicable information.
+
+## How to Submit Pull Requests
+
+### Development Workflow
+
+1. **Fork and Clone**: Fork this repository and clone your fork
+2. **Create Feature Branch**: Create a new topic branch based on `main`
+3. **Make Changes**: Implement your changes
+4. **Commit Changes**: See [commit guidelines](#pull-request-guidelines)
+
+### Pull Request Guidelines
+
+**Commit Requirements:**
+- Write clear, descriptive commit titles. Should fit under 50 characters
+- Write meaningful commit descriptions with each line having less than 72 characters
+- Split your contribution into several commits if applicable, each should represent a logical chunk
+- Add line `Assisted-by: <name-of-ai-tool>` if you used an AI tool for your contribution
+- Sign-off your commits in order to certify that you adhere to [Developer Certificate of Origin](https://developercertificate.org)
+
+**Pull Request Content:**
+- **Title**: Clear, descriptive title. Should fit under 72 characters.
+- **Description**: Explain the overall changes and their purpose, this should be a cover letter for your commits.
+- **Testing**: Describe how the changes were tested
+- **Links**: Reference related issues or upstream stories.
+
+**Remember:**
+- Konflux is a community project and proper descriptions cannot be replaced by referencing a publicly inaccessible link to Jira or any other private resource.
+- Reviewers, other contributors and future generations might not have the same context as you have at the moment of PR submission.
+
+### Security basics
+
+- Never commit secrets or keys to the repository
+- Never expose or log sensitive information
+
+## Review Process
+
+**Requirements for Approval:**
+- All CI checks pass
+- Code review approval from maintainers
+
+**Review Criteria:**
+- The contribution follows established patterns and conventions
+- Changes are tested and documented
+- Security best practices are followed
+
+For any questions or help with contributing, please open an issue or reach out to the maintainers.