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

make octokit instance available as octokit on top of github, to make it easier to seamlessly copy examples from GitHub rest api or octokit documentations#508

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

Merged
joshmgross merged 3 commits intoactions:mainfromiamstarkov:patch-2
Feb 4, 2025

Conversation

iamstarkov
Copy link
Contributor

@iamstarkoviamstarkov commentedJan 15, 2025
edited
Loading

examples on GitHubapi documentation use octokit as an octokit instance, so does theoctokit documentation itself. its kinda a bummer to always rename when you copy from documentation or from another files.

I understand that octokit was made available over the github keyword, and I dont want to break that, but it won't hurt nobody to expose octokit instance over the octokit keyword as well and it will help people who use documentation a lot

// api docsawaitoctokit.request('GET /repos/{owner}/{repo}/commits/{commit_sha}/pulls',{owner:'OWNER',repo:'REPO',commit_sha:'COMMIT_SHA',})// octokit documentationoctokit.rest.repos.listPullRequestsAssociatedWithCommit({  owner,  repo,  commit_sha,});

what do you think? if this is something you are up for adding, let me know and I adjust documentation accordingly

@iamstarkoviamstarkov requested a review froma team as acode ownerJanuary 15, 2025 18:22
@joshmgross
Copy link
Contributor

Thanks for the suggestion@iamstarkov - my one concern with this change is that users may assumeoctokitis Octokit and that could create additional confusion if something does not work as expected.

@iamstarkov
Copy link
ContributorAuthor

iamstarkov commentedJan 19, 2025
edited
Loading

my two cents would be that I used github-scripts heavily in the last few years and I'd not make that mistake, and also I think javascript developers are grown to know the difference Class and an instance.
That is to say, your concerns are not without merit, but I dont think we should underestimate developers. If we want, we have an option to remedy this potential issue by explicitly passing Octokit class explicitly

And my last argument will be that consistency with documentation will lead to net-smaller confusion after all. What do you think?

@joshmgross
Copy link
Contributor

@iamstarkov I'm fine with this change - could we update the documentation as well to make it clear that this is an option?

@iamstarkov
Copy link
ContributorAuthor

@joshmgross absolutely

iamstarkovand others added2 commitsJanuary 31, 2025 11:20
…it easier to seamless to copy examples from GitHub api or octokit documentation
@iamstarkov
Copy link
ContributorAuthor

@joshmgross updated documentation as we agreed, feel free to take a look

@iamstarkov
Copy link
ContributorAuthor

checked out project locally, adjusted types and committed updated dist folder accordingly

@iamstarkoviamstarkov changed the titlemake octokit instance available as octokit on top of github, to make it easier to seamless to copy examples from GitHub api or octokit documentationmake octokit instance available as octokit on top of github, to make it easier to seamlessly copy examples from GitHub rest api or octokit documentationsJan 31, 2025
@iamstarkov
Copy link
ContributorAuthor

iamstarkov commentedJan 31, 2025
edited
Loading

I have off topic to PR question, which i'm curious about

GitHub assigned this PR toa team without assigning anyone.

Screenshot 2025-01-31 at 12 00 05

isCODEOWNERS correct and@actions/actions-launch exists, but its not public?

@joshmgross
Copy link
Contributor

@iamstarkov yes that is a team, that's not my area of GitHub but my understanding is that organization teams are never public and can only be internal to all organization members or hidden.

iamstarkov reacted with thumbs up emoji

@iamstarkoviamstarkovtemporarily deployed to debug-integration-testFebruary 4, 2025 15:45 — withGitHub Actions Inactive
@joshmgrossjoshmgross merged commit378a50f intoactions:mainFeb 4, 2025
14 checks passed
@iamstarkoviamstarkov deleted the patch-2 branchFebruary 4, 2025 21:05
@iamstarkov
Copy link
ContributorAuthor

how does the release process look like for this action? I noticed41 unreleased commits since last release

joshmgross added a commit to joshmgross/actions-testing that referenced this pull requestFeb 26, 2025
This was referencedFeb 26, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@joshmgrossjoshmgrossjoshmgross approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@iamstarkov@joshmgross

[8]ページ先頭

©2009-2025 Movatter.jp