Confirm code generation during CI

Open
#738 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
ci-cd

Research direction

Start by reviewing PR #734 and the repository's CI configuration to identify how generated code is produced and checked. Done means CI detects when regeneration changes files and fails unless those generated changes are committed.

Written by the indexing model from the issue text.

Description

https://github.com/stretchr/testify/pull/734 was introduced to regenerate code that should have been included in the preceding PR. The repo CI should confirm any generated code is committed before passing to ensure this doesn't happen again.

Dominant language
Go
Stars
26.2k
Forks
1.9k
Avg merge
2d 4h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stretchr/testify

All issues in stretchr/testify

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.