JOJ/JOJ3
24
5
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

JOJ3 result as issue comments #71

New Issue
Closed
opened 2024-10-27 16:55:00 +08:00 by manuel · 6 comments
manuel commented 2024-10-27 16:55:00 +08:00
Owner
Copy Link

goal: a unique issue per task where each run posts a new comment

requirements

  • a "table of content" in the the 1st comment
  • each run post a new comment, this comment can be reach using a link in the 1st comment

example format for the 1st comment. each date/time is a link to corresponding comment in the issue

homework 2 exercise 3 records

JOJ called 3 times on a maximum of 5 runs

  • 10/10/2024 23:56 (feat(h2/e3): exercise competed joj)
  • 10/10/2024 23:58 (fix(h2/e3): consider case a=0 joj)
  • 11/10/2024 23:58 (refactor(h2/e3): faster algorithm for hard test cases joj)
goal: a unique issue per task where each run posts a new comment requirements - [ ] a "table of content" in the the 1st comment - [ ] each run post a new comment, this comment can be reach using a link in the 1st comment example format for the 1st comment. each date/time is a link to corresponding comment in the issue ## homework 2 exercise 3 records JOJ called 3 times on a maximum of 5 runs - 10/10/2024 23:56 (`feat(h2/e3): exercise competed joj`) - 10/10/2024 23:58 (`fix(h2/e3): consider case a=0 joj`) - 11/10/2024 23:58 (`refactor(h2/e3): faster algorithm for hard test cases joj`)
manuel added the
enhancement
component
UI
 labels 2024-10-27 16:55:00 +08:00
张泊明518370910136 changed title from JOj result as issue comments to JOJ3 result as issue comments 2024-10-27 19:09:04 +08:00
张泊明518370910136 commented 2024-10-27 20:15:41 +08:00
Owner
Copy Link

Since gitea issues have history recorded, it can be implemented just by editing the body of the issue.

Since gitea issues have history recorded, it can be implemented just by editing the body of the issue.
manuel commented 2024-10-27 20:41:39 +08:00
Author
Owner
Copy Link

sounds like the best stragegy. 1 unique issue pr task with 1 comment (with its history)

sounds like the best stragegy. 1 unique issue pr task with 1 comment (with its history)
张泊明518370910136 commented 2024-10-27 20:58:49 +08:00
Owner
Copy Link

Can we just edit the issue body as the JOJ3 result instead of the first comment?

Can we just edit the issue body as the JOJ3 result instead of the first comment?
manuel commented 2024-10-27 21:05:17 +08:00
Author
Owner
Copy Link

yes that's the best

yes that's the best
manuel commented 2024-10-27 21:05:49 +08:00
Author
Owner
Copy Link

even for tt that will be easy to see the what happened along the way

even for tt that will be easy to see the what happened along the way
张泊明518370910136 commented 2024-10-27 23:36:23 +08:00
Owner
Copy Link

Completed in f85b20e197.

Completed in https://github.com/BoYanZh/Joint-Teapot/commit/f85b20e1978e89b3aa228f0cd93a3d05d66a3313.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

Something is not working

  
component
executor
executors in different stages

  
component
framework
software architecture

  
component
parser
parsers in different stages

  
component
UI
drone, gitea, and config interfaces

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
priority
p0

  
priority
p1

  
priority
p2

  
priority
p3

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
bug
component
executor
component
framework
component
parser
component
UI
duplicate
enhancement
help wanted
invalid
priority
p0
priority
p1
priority
p2
priority
p3
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: JOJ/JOJ3#71
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?