commits  

Messages by Thread

• (answer-website) branch nginx created (now 1d3877635) shuai
  • (answer-website) 01/01: fix: add nginx.con file shuai
• [PR] Fix text [answer-website] via GitHub
  • Re: [PR] Fix text [answer-website] via GitHub
• (answer-website) branch fix-text deleted (was 9454fca0c) shuai
• (answer-website) branch main updated: Fix text (#298) shuai
• (answer-website) branch fix-text updated: fix: ci Add to run fetPlugin.js step shuai
• (answer-website) branch fix-text created (now 0e24ddf67) shuai
  • (answer-website) 01/01: fix: add scripts to get plugin data shuai
• (answer) branch dev updated (4232c464 -> ae13d687) linkinstar
  • (answer) 01/03: build(ci): update action upload-artifact to v4 linkinstar
  • (answer) 03/03: fix: i18n key of ready_desc linkinstar
  • (answer) 02/03: chore: update issue template (#1248) linkinstar
• [PR] fix: i18n key of ready_desc [answer] via GitHub
  • Re: [PR] fix: i18n key of ready_desc [answer] via GitHub
• (answer-website) branch main updated: fix: copywriting adjustment (#297) shuai
• (answer-website) branch fix-text created (now c4999e999) shuai
  • (answer-website) 01/01: fix: copywriting adjustment shuai
• (answer-website) branch fix-text deleted (was c4999e999) shuai
• [PR] fix: copywriting adjustment [answer-website] via GitHub
  • Re: [PR] fix: copywriting adjustment [answer-website] via GitHub
• (answer) branch test updated: fix: preview mode icon toggle shuai
• Re: [PR] Add Easypanel as a deployment method [answer-website] via GitHub
• [PR] chore: fix issue label and team role [answer-website] via GitHub
  • Re: [PR] chore: fix issue label and team role [answer-website] via GitHub
• (answer) branch main updated: chore: update issue template (#1248) fenbox
• [PR] chore: update issue template [answer] via GitHub
  • Re: [PR] chore: update issue template [answer] via GitHub
• (answer) branch test updated (fb152cb3 -> f6fdc5f5) linkinstar
  • (answer) 01/01: Merge branch 'dev' into test linkinstar
• (answer-website) branch docs/security-model updated: docs/community: update security model documentation and sidebar linkinstar
• (answer-website) branch docs/security-model created (now fc80657ee) linkinstar
  • (answer-website) 01/01: docs(docusaurus): add security model documentation linkinstar
• (answer) branch test updated: fix: optimize copy button style shuai
• (answer) branch test updated: fix: the list page introduction adopts the way of rendering rich text to support the display of some special symbols shuai
• (answer) branch revert-1234-dev deleted (was 4499b41e) shuai
• (answer) branch dev updated (e0957c0a -> 4232c464) shuai
  • (answer) 01/02: Revert "refactor: refactor show password logic in init answer app" shuai
  • (answer) 02/02: Revert "feat: add password hide show logic for init server" shuai
• [PR] Revert "feat: add password hide show logic for init server" [answer] via GitHub
  • Re: [PR] Revert "feat: add password hide show logic for init server" [answer] via GitHub
• (answer) branch revert-1234-dev created (now 4499b41e) shuai
  • (answer) 02/02: Revert "feat: add password hide show logic for init server" shuai
  • (answer) 01/02: Revert "refactor: refactor show password logic in init answer app" shuai
• (answer) branch dev updated: Revert "perf: optimize tag has new tag check" linkinstar
• [PR] revert: fix HasNewTag return value inconsistency in TagCommonService (#1245) [answer] via GitHub
  • Re: [PR] revert: fix HasNewTag return value inconsistency in TagCommonService [answer] via GitHub
• [I] HasNewTag in TagCommonService's return value may not be right [answer] via GitHub
  • Re: [I] HasNewTag in TagCommonService's return value may not be right [answer] via GitHub
  • Re: [I] HasNewTag in TagCommonService's return value may not be right [answer] via GitHub
• (answer) branch dev updated (4af744e7 -> e9412a44) shuai
  • (answer) 01/03: Answer-1237: Add dependent command 'install-ui-packages' to 'make ui' command shuai
  • (answer) 03/03: Answer-1237: Remove dependent command 'install-ui-packages' to 'make ui' command shuai
  • (answer) 02/03: Answer-1237: Add missing old_pass object message to i18n shuai
• (answer-website) branch main updated: release: bump version to 1.4.2 and update release date linkinstar
• [PR] release: bump version to 1.4.2 and update release date [answer-website] via GitHub
  • Re: [PR] release: bump version to 1.4.2 and update release date [answer-website] via GitHub
• [PR] 1.4.2 release [answer-website] via GitHub
  • Re: [PR] 1.4.2 release [answer-website] via GitHub
• (answer-website) branch docs/1.4.2 updated: docs(release): update 1.4.2 release blog\ linkinstar
• (answer-website) branch docs/1.4.2 deleted (was dd17d7139) linkinstar
• (answer-website) branch main updated (6f1dc33d3 -> f6ca8c72c) linkinstar
  • (answer-website) 02/02: docs(release): update 1.4.2 release blog\ linkinstar
  • (answer-website) 01/02: docs(blog): announce Apache Answer 1.4.2 release linkinstar
• svn commit: r74811 - in /release/answer: 1.4.2-RC2/ 1.4.2/ linkinstar
• svn commit: r74810 - /dev/answer/1.4.2-RC2/ /release/answer/1.4.2-RC2/ mingcheng
• [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
  • Re: [PR] Support PostgreSQL connection with SSL #1243 [answer] via GitHub
  • Re: [PR] Support PostgreSQL connection with SSL #1243 [answer] via GitHub
  • Re: [PR] Support PostgreSQL connection with SSL #1243 [answer] via GitHub
  • Re: [PR] front end and backend added for the feature #1243 [answer] via GitHub
• [I] PostgreSQL connection with SSL [answer] via GitHub
  • Re: [I] PostgreSQL connection with SSL [answer] via GitHub
• Re: [I] Add category options for default filtering on home page [answer] via GitHub
  • Re: [I] Add category options for default filtering on home page [answer] via GitHub
  • Re: [I] Add category options for default filtering on home page [answer] via GitHub
• (answer) tag v1.4.2 created (now 0fd7e81a) linkinstar
• (answer) branch main updated: build(ci): update action upload-artifact to v4 linkinstar
• (answer) branch ci deleted (was c8fb168a) linkinstar
• (answer) branch ci created (now c8fb168a) linkinstar
  • (answer) 01/01: build(ci): update action upload-artifact to v4 linkinstar
• [PR] build(ci): update action upload-artifact to v4 [answer] via GitHub
  • Re: [PR] build(ci): update action upload-artifact to v4 [answer] via GitHub
• (answer) tag v1.4.2 deleted (was 5886c1ec) linkinstar
• (answer) tag v1.4.2 created (now 5886c1ec) linkinstar
• (answer) branch dev updated: Remove fixed width Share Popup robin0716
• [I] How to debug using VSCode? [answer] via GitHub
  • Re: [I] How to debug using VSCode? [answer] via GitHub
  • Re: [I] How to debug using VSCode? [answer] via GitHub
• [I] Favicon Mixed Content: The page at 'https://example.com:1340/users/xxx' was loaded over HTTPS, but requested an insecure favicon 'http://ip:9080/uploads/branding/5nPxxxxxE.png'. This request has been blocked; the content must be served over HTTPS. [answer] via GitHub
  • Re: [I] Favicon Mixed Content: The page at 'https://example.com:1340/users/xxx' was loaded over HTTPS, but requested an insecure favicon 'http://ip:9080/uploads/branding/5nPxxxxxE.png'. This request has been blocked; the content must be served over HTTPS. [answer] via GitHub
• [PR] feat: Copy code button [answer] via GitHub
  • Re: [PR] feat: Copy code button [answer] via GitHub
  • Re: [PR] feat: Copy code button [answer] via GitHub
  • Re: [PR] feat: Copy code button [answer] via GitHub
  • Re: [PR] feat: Copy code button [answer] via GitHub
  • Re: [PR] feat: Copy code button [answer] via GitHub
• [PR] Answer issue: 1237 [answer] via GitHub
  • Re: [PR] Answer issue: 1237 [answer] via GitHub
  • Re: [PR] Answer issue: 1237 [answer] via GitHub
  • Re: [PR] Answer issue: 1237 [answer] via GitHub
• (answer-website) branch blog deleted (was a028f3d5a) joyqi
• (answer-website) branch main updated: update: add new blog (#293) joyqi
• (answer-website) branch blog updated (5c6a02f66 -> a028f3d5a) joyqi
• [PR] update: add new blog [answer-website] via GitHub
  • Re: [PR] update: add new blog [answer-website] via GitHub
  • Re: [PR] update: add new blog [answer-website] via GitHub
• (answer-website) branch blog created (now 5c6a02f66) joyqi
  • (answer-website) 01/01: update: add new blog joyqi
• [I] Local run simple issues [answer] via GitHub
  • Re: [I] Local run simple issues [answer] via GitHub
  • Re: [I] Local run simple issues [answer] via GitHub
  • Re: [I] Local run simple issues [answer] via GitHub
  • Re: [I] Local run simple issues [answer] via GitHub
• [PR] Remove fixed width Share Popup [answer] via GitHub
  • Re: [PR] Remove fixed width Share Popup [answer] via GitHub
• [I] Building plugins with docker results in a successful build with no plugins installed [answer] via GitHub

• Earlier messages
• Later messages