Current state of the template

Open
#76 0 comments 0 reactions 4 assignees View on GitHub

@ahms5 is already working on this.

Since Nov 6, 2026.

Assessment

This issue has not been assessed yet.

Description

  • Current state:
    The code is almost finished: the templates for PRs (PR #44) and Issues (PR #24) need to be added, as well as a workflow to automatically update the existing packages whenever the template is updated (PR #56).

  • ToDOs:

    1. Review and approve the existing pull requests.
    2. Test the template by at least two people who were not involved in its development.
    3. Review, or at least check, every pull request titled "Migrate to copier" in each package. Here is the link to the issue that collects the links to all "Migrate to copier" pull requests in the different packages.
  • Help needed? - Yes, at least with the review of existing PRs. But opinions on the whole project are also very much appreciated

(edited by @h-chmeruk )

  • would be nice e.g. for updating deprecation tests or python 3.15

Suggestion by @mberz:

At least 2 people try the copier template in the current state to set up a new project ☑️

Dominant language
Jinja
Stars
0
Forks
0
Avg merge
4d 16h
Merged PRs (30d)
2

Getting set up

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 pyfar/template-pyfar-package

All issues in pyfar/template-pyfar-package

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.