You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,13 +12,14 @@ Please include a summary of the change and include relevant motivation and conte
12
12
-[ ] Any new code follows the style guidelines of this project.
13
13
-[ ] The code changes have been self-reviewed.
14
14
-[ ] Corresponding changes to the documentation have been made.
15
-
-[ ] The version has been updated in the VERSION file.
15
+
16
+
> The maintainer bumps the `VERSION` file at release time. Do not change it in your PR.
16
17
17
18
## Type of change:
18
19
19
-
-[ ] Minor non-breaking change (e.g., bug fix, dependencies updates) → The patch number in the VERSION file has been increased.
20
-
-[ ] New feature (non-breaking change which adds functionality) → The minor number in the VERSION file has been increased.
21
-
-[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) → The major number in the VERSION file has been increased.
20
+
-[ ] Minor non-breaking change (e.g., bug fix, dependencies updates).
21
+
-[ ] New feature (non-breaking change which adds functionality).
22
+
-[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+12-5Lines changed: 12 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,8 @@ Thank you for your interest in contributing to **tc-lib-pdf** — the modern evo
4
4
5
5
Please take a moment to read this guide before opening an issue or pull request.
6
6
7
+
> **Pull requests are restricted to project collaborators.** If you are not a collaborator, please [open an issue](https://github.com/tecnickcom/tc-lib-pdf/issues) instead of a pull request, describing the bug or feature in detail. A maintainer will review it and take it from there.
8
+
7
9
---
8
10
9
11
## Table of Contents
@@ -83,7 +85,11 @@ The more precise and reproducible the report, the faster it can be triaged and f
83
85
84
86
## Submitting a Bug Fix
85
87
86
-
1.[Fork the repository](https://github.com/tecnickcom/tc-lib-pdf/fork) and create a branch from `main`:
88
+
> Only project collaborators can open pull requests. If you are not a collaborator, please [open an issue](https://github.com/tecnickcom/tc-lib-pdf/issues/new) describing the bug in detail (see [Reporting a Bug](#reporting-a-bug)). A maintainer will take it from there.
89
+
90
+
Collaborators preparing a fix:
91
+
92
+
1. Create a branch from `main`:
87
93
```bash
88
94
git checkout -b fix/short-description-of-bug
89
95
```
@@ -94,9 +100,7 @@ The more precise and reproducible the report, the faster it can be triaged and f
94
100
make qa
95
101
```
96
102
5. Commit your changes (see [Commit Message Guidelines](#commit-message-guidelines)).
97
-
6. Open a pull request against `main` and fill in the PR template:
98
-
- Describe the problem and your solution.
99
-
- Reference the related issue number (e.g. `Fixes #123`).
103
+
6. Open a pull request against `main` and fill in the PR template, describing the problem and your solution and referencing the related issue number (e.g. `Fixes #123`).
100
104
101
105
---
102
106
@@ -107,7 +111,7 @@ Before writing any code:
107
111
1.**Open a Feature Request** on [GitHub Issues](https://github.com/tecnickcom/tc-lib-pdf/issues/new) describing the use case and proposed API.
108
112
2. Wait for feedback from the maintainer. This avoids investing time in a direction that may not be accepted.
109
113
110
-
Once the feature is agreed upon, follow the same branch → code → test → PR workflow as for bug fixes, using a branch named `feature/short-description`.
114
+
Once the feature is agreed upon, a collaborator will implement it following the same branch → code → test → pull request workflow as for bug fixes, using a branch named `feature/short-description`.
111
115
112
116
---
113
117
@@ -163,6 +167,9 @@ Coverage reports are generated in `target/coverage/`.
163
167
164
168
## Pull Request Guidelines
165
169
170
+
> Opening pull requests is restricted to project collaborators. If you are an external contributor, please [open an issue](https://github.com/tecnickcom/tc-lib-pdf/issues/new) describing the problem or feature in detail instead.
171
+
172
+
-**Sign the Contributor License Agreement (CLA).** On your first pull request the CLA Assistant bot will comment with a link to sign; the PR cannot be merged until the CLA is signed.
166
173
- Target the `main` branch.
167
174
- Keep PRs focused — one fix or feature per PR.
168
175
- Ensure `make qa` passes locally before opening the PR.
Copy file name to clipboardExpand all lines: examples/index.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ This index lists all runnable examples bundled with tc-lib-pdf, from foundationa
5
5
-[E000_overview.php](E000_overview.php): General feature overview with text, graphics, HTML, SVG, images, barcodes, transparency, gradients, annotations, and bookmarks.
6
6
-[E001_invoice.php](E001_invoice.php): Invoice layout example with embedded Factur-X / ZUGFeRD metadata.
7
7
-[E002_font_dump.php](E002_font_dump.php): Font inspection and glyph dump example.
8
-
-[E003_rtl_languages.php](E003_rtl_languages.php): Right-To-Left (RTL) text rendering example for Persian, Arabic and Hebrew.
8
+
-[E003_rtl_languages.php](E003_rtl_languages.php): Right-To-Left (RTL) text rendering example for Persian, Arabic, and Hebrew.
9
9
-[E004_page_formats.php](E004_page_formats.php): Page format and orientation samples.
10
10
-[E005_header_footer.php](E005_header_footer.php): Repeating custom page header and footer example with PDF/UA Artifact tagging (`Pagination/Header` and `Pagination/Footer`).
-[E074_text_cell_fit_modes.php](E074_text_cell_fit_modes.php): Visual inspection grid for getTextCell() fit modes (T, S, F) including disabled precondition cases.
80
80
-[E075_external_signature_injection.php](E075_external_signature_injection.php): External/remote signing walkthrough using signature placeholder setup, ByteRange digest export, and injected CMS/PKCS#7 signature bytes.
81
-
-[E076_absolute_position.php](E076_absolute_position.php): Absolute coordinates position inside a give page.
81
+
-[E076_absolute_position.php](E076_absolute_position.php): Absolute coordinate positioning within a given page.
82
82
-[E077_html_table_header_px_unit.php](E077_html_table_header_px_unit.php): HTML table pagination with px document units, verifying replayed header rows keep the same column geometry on continuation pages.
83
83
-[E078_htmlcell_page_margins.php](E078_htmlcell_page_margins.php): Single page with 100mm top and bottom margins, placing getHTMLCell text blocks in the top border, central content area, and bottom border.
84
84
-[E079_font_stretch_spacing_matrix.php](E079_font_stretch_spacing_matrix.php): Font stretching (Tz) and character spacing (Tc) matrix across L/C/R/J alignment for both the direct text API and the HTML/CSS font-stretch/letter-spacing engine.
0 commit comments