mikyll opened a new issue, #1952:
URL: https://github.com/apache/apisix-website/issues/1952

   ### Current State
   
   **Description of the current state/issue**:
   
   It seems like PR links are shifted by 1 below, in blog posts about Monthly 
Reports. I noticed that the section URLs are shifted by one: When you click on 
the `#` next to the heading of an element of the list, it copies the URL with 
wrong section (e.g. 
   
   **Link to the page**:
   
   - https://apisix.apache.org/blog/2025/08/31/2025-august-monthly-report/
     - 3\. Allow Environment Variables in `openid-connect` Plugin | the PR link 
points to [#12530](https://github.com/apache/apisix/pull/12530) instead of 
[#12509](https://github.com/apache/apisix/pull/12509)
     - 4\. Add Healthcheck Support for `ai-proxy-multi` Plugin | the PR link 
points to [#11451](https://github.com/apache/apisix/pull/11451) instead of 
[#11451](https://github.com/apache/apisix/pull/11451)
     - 5\. Add Latency and Token Usage in Access Log and Prometheus Metrics in 
`ai-proxy Plugin` | the PR link points to 
[#12509](https://github.com/apache/apisix/pull/12509) instead of 
[#12518](https://github.com/apache/apisix/pull/12518)
     - ...
   
   - https://apisix.apache.org/blog/2025/08/31/2025-august-monthly-report/
     - 5\. Store JWT in the Request Context in `jwt-auth` Plugin | the PR link 
points to [#12004](https://github.com/apache/apisix/pull/12004) instead of 
[#11675](https://github.com/apache/apisix/pull/11675);
       the `#` copies the section of the element before: "4. Support Proxying 
OpenAI-Compatible LLMs", 
[#4-support-proxying-openai-compatible-llms](https://apisix.apache.org/blog/2025/03/31/2025-march-monthly-report/#4-support-proxying-openai-compatible-llms)
     - ...
   
   
   ### Desired State
   
   **Description of the change you are proposing**:
   
   Links should point to the correct URLs
   
   ### Would you like to fix this issue?
   
   Yes! Count me in


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to