fix python example in generating-a-json-web-token-jwt-for-a-github-app

[gregsadetsky]

Why:

Closes: #39408

What's being changed (if available, include any code snippets, screenshots, or gifs):

the python example has been fixed

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[Copilot]

Pull Request Overview

This PR fixes the Python code example in the GitHub App JWT generation documentation to use the correct PyJWT library API. The changes update the outdated jwt module usage to the modern JWT class-based approach with proper key handling.

Key changes:

• Updates import statement to use the modern JWT class and jwk_from_pem function
• Modifies key loading to use jwk_from_pem for proper PEM file handling
• Changes JWT encoding to use the instance-based approach with updated parameter names

[Copilot]

The parameter name change from 'algorithm' to 'alg' should be documented or explained in the surrounding text to help users understand why this change was made, especially since this differs from the previous API.

Suggested change

	instance = JWT()
	instance = JWT()
	# The 'alg' parameter specifies the algorithm used for signing the JWT.
	# It corresponds to the 'algorithm' parameter in the previous API.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
apps/creating-github-apps/authenticating-with-a-github-app/generating-a-json-web-token-jwt-for-a-github-app.md	fpt ghec ghes@ 3.17 3.16 3.15 3.14	fpt ghec ghes@ 3.17 3.16 3.15 3.14

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

@gregsadetsky Thanks for opening an issue and PR! I'll get this triaged for review.

[Sharra-writes]

@gregsadetsky My co-worker tells me this is essentially a reversion to an earlier state, but agrees it's not a bad move currently. The only thing is that on line 79, the pip install PyJWT cryptography should actually read pip install pyjwt cryptography. Just that first instance needs to be all lowercase. Would you be willing to make that change so I don't have to open a separate PR for it?

[gregsadetsky]

@Sharra-writes oh my God, this is super embarrassing ... I actually didn't fully follow the original tutorial and used a different jwt library.

The library that you're using seems a lot more standard. And so, the example in the docs wasn't wrong at all...

I'm really sorry! I'll just close this PR then, yeah?

[Sharra-writes]

@gregsadetsky It's no problem! I can close it for you. Thanks for reaching out to improve things, even if it went a bit sideways this time. We still appreciate the effort and concern.

[gregsadetsky]

A good slice of humble pie for me! Haha. Cheers & thank you