Re: [PR] Convert apt to markdown [maven-site]

2025-03-17 Thread via GitHub
slachiewicz commented on PR #728: URL: https://github.com/apache/maven-site/pull/728#issuecomment-2729615537 I've used instructions from https://github.com/apache/maven-site/pull/573#issue-2621918965 but forgot about this switch. You are right - we should keep git history. -- Thi

Re: [PR] Convert apt to markdown [maven-site]

2025-03-17 Thread via GitHub
slachiewicz closed pull request #728: Convert apt to markdown URL: https://github.com/apache/maven-site/pull/728 -- 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,

Re: [PR] Convert apt to markdown [maven-site]

2025-03-17 Thread via GitHub
slachiewicz commented on PR #728: URL: https://github.com/apache/maven-site/pull/728#issuecomment-2729550049 Yes. When I attempted to convert part by part, I realized that we have many subdirectories in each file. So it's more time-consuming to open different PR etc. And unfortunately,

Re: [PR] Convert apt to markdown [maven-site]

2025-03-16 Thread via GitHub
Bukama commented on PR #728: URL: https://github.com/apache/maven-site/pull/728#issuecomment-2728094491 I like getting progress here as I still wait for Konrads announced updates in his PR (didn't want to just take over, after he announcced he will update). However I'm a bit curious about y

[PR] Convert apt to markdown [maven-site]

2025-03-16 Thread via GitHub
slachiewicz opened a new pull request, #728: URL: https://github.com/apache/maven-site/pull/728 (no comment) -- 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,