Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Prototype tuxctl#27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Draft
Gijsreyn wants to merge5 commits intoPowerShell:main
base:main
Choose a base branch
Loading
fromGijsreyn:prototype-tuxctl

Conversation

@Gijsreyn
Copy link

PR Summary

This PR adds a prototype Python DSC resource for user management.

PR Checklist

  • Descriptive Title: This PR's title is a synopsis of the changes it proposes.
  • Summary: This PR's summary describes the scope and intent of the change.
  • Contributor's Guide: I have read thecontributors guide.
  • Style: This PR adheres to thestyle guide.

@github-actions
Copy link

Expectations

Thanks for your submission! Here's a quick note to provide you with some context for what to expectfrom the docs team and the process now that you've submitted a PR. Even if you've contributed tothis repo before, we strongly suggest reading this information; it might have changed since you lastread it.

This is a brief, high-level summary of what to expect from this process.

The team begins to review your PR if yourequest them to or if your PRmeets these conditions:

  • It's not adraft PR.
  • It doesn't have aWIP prefix in the title.
  • It passes validation and build steps.
  • It doesn't have any merge conflicts.
  • You have checked every box in thePR Checklist, indicating you have completed allrequired steps and marked your PR asReady to Merge.

You canalways request a review at any stage in your authoring process, the team is here tohelp! You don't need to submit a fully polished and finished draft; the team can help you getcontent ready for merge.

While reviewing your PR, the team may make suggestions, write comments, and ask questions. When allrequirements are satisfied, the team marks your PR asApproved and merges it. Once your PR'smerged, it's included when the site rebuilds.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@sdwheelersdwheelerAwaiting requested review from sdwheelersdwheeler will be requested when the pull request is marked ready for reviewsdwheeler is a code owner

@michaeltlombardimichaeltlombardiAwaiting requested review from michaeltlombardimichaeltlombardi will be requested when the pull request is marked ready for reviewmichaeltlombardi is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Gijsreyn

[8]ページ先頭

©2009-2025 Movatter.jp