Skip to content

Actions: antvis/G6

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
7,601 workflow runs
7,601 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

fix: fix new node invisible after invoke graph.clear No response #224: Issue comment #6702 (comment) created by petercat-assistant bot
January 7, 2025 12:09 8s
January 7, 2025 12:09 8s
No response No response #223: Scheduled
January 7, 2025 12:09 9s v5
v5
January 7, 2025 12:09 9s
fix: fix new node invisible after invoke graph.clear build #724: Commit 5e1fee5 pushed by Aarebecca
January 7, 2025 12:07 8m 21s fix/clear-draw
fix/clear-draw
January 7, 2025 12:07 8m 21s
[Bug]: After changeData, the result of changing the edge state item.setState does not meet expectations Translate Issue Title #276: Issue #6701 edited by Cherry860
January 7, 2025 12:06 14s
January 7, 2025 12:06 14s
[Bug]: After changeData, the result of changing the edge state item.setState does not meet expectations Translate Issue Title #275: Issue #6701 opened by Cherry860
January 7, 2025 12:05 15s
January 7, 2025 12:05 15s
[Bug]: After changeData, the result of changing the edge state item.setState does not meet expectations Auto Close Issue #1273: Issue #6701 labeled by Cherry860
January 7, 2025 12:05 13s
January 7, 2025 12:05 13s
pages build and deployment pages-build-deployment #146: by hustcc
January 7, 2025 11:42 58s gh-pages
gh-pages
January 7, 2025 11:42 58s
[Bug]: When the 'opacity' property is set to the state of a node, the state of the node is not restored after the 'hover-activate' event ends No response #222: Issue comment #6700 (comment) created by petercat-assistant bot
January 7, 2025 11:34 13s
January 7, 2025 11:34 13s
[Bug]: When the 'opacity' property is set to the state of a node, the state of the node is not restored after the 'hover-activate' event ends Translate Issue Title #274: Issue #6700 opened by zh-lx
January 7, 2025 11:34 13s
January 7, 2025 11:34 13s
[Bug]: When the 'opacity' property is set to the state of a node, the state of the node is not restored after the 'hover-activate' event ends Auto Close Issue #1272: Issue #6700 labeled by zh-lx
January 7, 2025 11:34 11s
January 7, 2025 11:34 11s
fix: fix edges which connect to combo were filtered in layout stage Auto Publish #225: Pull request #6698 closed by Aarebecca
January 7, 2025 11:30 2s fix/layout-data
fix/layout-data
January 7, 2025 11:30 2s
fix: fix edges which connect to combo were filtered in layout stage (… Deploy #582: Commit 9b21901 pushed by Aarebecca
January 7, 2025 11:30 12m 28s v5
v5
January 7, 2025 11:30 12m 28s
fix: fix edges which connect to combo were filtered in layout stage (… build #723: Commit 9b21901 pushed by Aarebecca
January 7, 2025 11:30 9m 4s v5
v5
January 7, 2025 11:30 9m 4s
[Bug]: When the orthogonal router orth configuration is used for discounted polyline, the edge display is not normal, and there will be problems such as occlusion Auto Close Issue #1271: Issue #6696 labeled by yvonneyx
January 7, 2025 03:10 8s
January 7, 2025 03:10 8s
[Bug]: When the orthogonal router orth configuration is used for discounted polyline, the edge display is not normal, and there will be problems such as occlusion No response #221: Issue comment #6696 (comment) created by yvonneyx
January 7, 2025 03:10 12s
January 7, 2025 03:10 12s
[Bug]: When the orthogonal router orth configuration is used for discounted polyline, the edge display is not normal, and there will be problems such as occlusion No response #220: Issue comment #6696 (comment) created by ChenKun1997
January 7, 2025 03:04 11s
January 7, 2025 03:04 11s
[Bug]: When the orthogonal router orth configuration is used for discounted polyline, the edge display is not normal, and there will be problems such as occlusion Auto Close Issue #1270: Issue #6696 labeled by yvonneyx
January 7, 2025 02:56 7s
January 7, 2025 02:56 7s
[Bug]: When the orthogonal router orth configuration is used for discounted polyline, the edge display is not normal, and there will be problems such as occlusion No response #219: Issue comment #6696 (comment) created by yvonneyx
January 7, 2025 02:56 12s
January 7, 2025 02:56 12s
fix: fix edges which connect to combo were filtered in layout stage No response #218: Issue comment #6698 (comment) created by petercat-assistant bot
January 7, 2025 02:42 9s
January 7, 2025 02:42 9s
fix: fix edges which connect to combo were filtered in layout stage build #722: Commit 294072d pushed by Aarebecca
January 7, 2025 02:41 9m 32s fix/layout-data
fix/layout-data
January 7, 2025 02:41 9m 32s
No response No response #217: Scheduled
January 7, 2025 00:25 12s v5
v5
January 7, 2025 00:25 12s
No response No response #216: Scheduled
January 6, 2025 12:09 9s v5
v5
January 6, 2025 12:09 9s
[v5] combo布局异常 No response #215: Issue comment #5988 (comment) created by liaodalin19903
January 6, 2025 09:15 10s
January 6, 2025 09:15 10s
[Bug]: Custom edges obscure nodes No response #214: Issue comment #6692 (comment) created by ChenKun1997
January 6, 2025 09:07 11s
January 6, 2025 09:07 11s
[Bug]: When the orthogonal router orth configuration is used for discounted polyline, the edge display is not normal, and there will be problems such as occlusion No response #213: Issue comment #6696 (comment) created by petercat-assistant bot
January 6, 2025 03:45 10s
January 6, 2025 03:45 10s