forge/forge
11
8
Fork 8
Code Issues 95 Pull requests 1 Projects Wiki Activity Actions

Private Issues: Refactor sql.NullInt64 to optional.Option #583

New issue
Closed
opened 2026-05-19 15:37:47 +00:00 by nphilipp · 2 comments
nphilipp commented 2026-05-19 15:37:47 +00:00
Member
Copy link

Story

As a developer in the Forgejo codebase,
I want that optional struct fields are implemented consistently,
so that I don’t have to keep mental models in my head unnecessarily.

Acceptance Criteria

  • The current way of using sql.NullInt64 types for these fields is replaced by optional.Option[…].
  • Users of these fields are updated accordingly.
  • Unit tests pass (make … test-backend)
  • Integration tests pass (make … test-sqlite)
  • Changes are integrated with our previous commits that they change

Background

Upstream prefers using optional.Option[…] over sql.NullInt64, it’s got some (better?) testing coverage.

# Story As a developer in the Forgejo codebase, I want that optional struct fields are implemented consistently, so that I don’t have to keep mental models in my head unnecessarily. # Acceptance Criteria - [x] The current way of using `sql.NullInt64` types for these fields is replaced by `optional.Option[…]`. - [x] Users of these fields are updated accordingly. - [x] Unit tests pass (`make … test-backend`) - [x] Integration tests pass (`make … test-sqlite`) - [x] Changes are integrated with our previous commits that they change # Background Upstream [prefers](https://codeberg.org/forgejo/design/issues/2#issuecomment-14633643) using `optional.Option[…]` over `sql.NullInt64`, it’s got some (better?) testing coverage.
nphilipp added this to the Sprint 21 project 2026-05-19 15:37:48 +00:00
nphilipp changed title from Private Issues: Refactor sql.NullInt64 to optional.Optional to Private Issues: Refactor sql.NullInt64 to optional.Option 2026-05-19 15:39:11 +00:00
nphilipp commented 2026-05-29 11:26:27 +00:00
Author
Member
Copy link

Bumping SPs, as it proved to be more involved than I initially thought.

Bumping SPs, as it proved to be more involved than I initially thought.
nphilipp commented 2026-06-01 08:08:54 +00:00
Author
Member
Copy link

The changes are in the fedora fork, in these branches:

The changes are in the `fedora` fork, in these branches: - [private-issues-backend](https://codeberg.org/fedora/forgejo/src/branch/private-issues-backend) - [private-issues](https://codeberg.org/fedora/forgejo/src/branch/private-issues)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
test
docs
No results found.
Labels
Clear labels   
ai-review-please
label for requesting AI code review

  
Org/Team Modification

   
Private Issues
Label for tracking development on Private Issues in Forgejo

  
Runner Request
  
Backlog Status
Needs Review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
High
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
 Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
 Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
 Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt
Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
 Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
 Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
 User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
ai-review-please
Org/Team Modification
Private Issues
Runner Request
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint 21
Assignees
Clear assignees
No assignees
nphilipp
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#585 Private Issues: Get foundational changes integrated upstream
forge/forge
#594 Private Issues: “Privatize” Comments
forge/forge
Reference
forge/forge#583
No description provided.