Skip to content

Conversation

@michaltomczuk
Copy link
Contributor

@michaltomczuk michaltomczuk commented Sep 30, 2022

What changes does your PR bring?

Personalize the newly created repository.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Chore (non-breaking change to the build process or auxiliary tools)
  • New feature (non-breaking change which adds functionality)
  • Documentation (Improvements or additions to documentation)
  • Breaking change (fix or feature that would cause existing functionality not to work as expected)

References

Fixes: #2

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented on my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

@michaltomczuk michaltomczuk added the documentation Improvements or additions to documentation label Sep 30, 2022
@michaltomczuk michaltomczuk self-assigned this Sep 30, 2022
@michaltomczuk michaltomczuk requested a review from a team as a code owner September 30, 2022 09:40
@michaltomczuk michaltomczuk linked an issue Sep 30, 2022 that may be closed by this pull request
2 tasks
@michaltomczuk michaltomczuk merged commit f5b7bb8 into main Sep 30, 2022
@michaltomczuk michaltomczuk deleted the 2-prepare-customize-newly-created-reposiotory branch September 30, 2022 10:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Prepare (customize) newly created reposiotory

2 participants