saveourtool/save-cloud

Save information about who triggered the run

Open

#813 opened on Jun 2, 2022

View on GitHubContributor guide
 (1 comment) (0 reactions) (1 assignee)Kotlin (4 forks)github user discovery
enhancementgood first issuesave-release

Repository metrics

Stars
 (38 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

On execution level in history of executions we should know who triggered the execution.

Contributor guide

Research direction
Identify where execution history is stored (model, database, repository). Add a field to track the user who triggered the run and update relevant API endpoints and UI if necessary.
Tech stack
kotlin
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KotlinDatabase basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55