kimyenac opened a new pull request, #5299: URL: https://github.com/apache/zeppelin/pull/5299
### What is this PR for? The Zeppelin UI still contained several direct `http://zeppelin.apache.org` links. The public Zeppelin site is served over HTTPS, and newer links in the codebase already use HTTPS. This PR switches the UI-facing website links from `http://` to `https://` and updates the focused E2E expectation that pinned the old scheme. Changes (5 files, 7 links): - `zeppelin-web-angular/src/app/pages/workspace/home/home.component.html` — documentation & community links - `zeppelin-web-angular/src/app/share/about-zeppelin/about-zeppelin.component.html` — "Get involved!" link - `zeppelin-web-angular/e2e/tests/home/home-page-external-links.spec.ts` — community-link expectation - `zeppelin-web/src/app/home/home.html` — documentation & community links (classic UI) - `zeppelin-web/src/components/navbar/navbar.html` — "Get involved!" link (classic UI) Non-Zeppelin links (e.g. `www.apache.org/licenses/LICENSE-2.0`), version placeholders, and unrelated docs are intentionally left unchanged. ### What type of PR is it? Improvement ### What is the Jira issue? [ZEPPELIN-6494](https://issues.apache.org/jira/browse/ZEPPELIN-6494) ### How should this be tested? - Search the touched UI files and confirm no `http://zeppelin.apache.org` remains: ``` rg -n "http://zeppelin.apache.org"; zeppelin-web-angular/src/app/pages/workspace/home/home.component.html zeppelin-web-angular/src/app/share/about-zeppelin/about-zeppelin.component.html zeppelin-web-angular/e2e/tests/home/home-page-external-links.spec.ts zeppelin-web/src/app/home/home.html zeppelin-web/src/components/navbar/navbar.html ``` - `cd zeppelin-web-angular && npm run lint` — passes with no errors. ### Questions: - Does the license apply to the code changes? Yes -- 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]
