Skip to content

update Slack invitation links#21874

Closed
martin-mfg wants to merge 1 commit intoOpenAPITools:masterfrom
martin-mfg:slack-invitation-update-2
Closed

update Slack invitation links#21874
martin-mfg wants to merge 1 commit intoOpenAPITools:masterfrom
martin-mfg:slack-invitation-update-2

Conversation

@martin-mfg
Copy link
Copy Markdown
Contributor

Update all links to Slack, because the old invitation expired.

PR checklist

  • Read the contribution guidelines.
  • Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
  • Run the following to build the project and update samples:
    ./mvnw clean package || exit
    ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
    ./bin/utils/export_docs_generators.sh || exit
    
    (For Windows users, please run the script in WSL)
    Commit all changed files.
    This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
    These must match the expectations made by your contribution.
    You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
    IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
  • File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
  • If your PR solves a reported issue, reference it using GitHub's linking syntax (e.g., having "fixes #123" present in the PR description)
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@wing328
Copy link
Copy Markdown
Member

wing328 commented Sep 3, 2025

Screenshot 2025-09-03 140955

that's what i got using private mode in browser.

what error message did you get?

@martin-mfg
Copy link
Copy Markdown
Contributor Author

Slackbot warned me some days ago that the invitation link I created would expire soon. Clicking the "Renew Link" button didn't work. Yesterday evening the link indeed expired:

grafik

"Somebody tried joining openapi-generator via your invitation link, which is already expired."

"Oh no, something went wrong. Please try again."

And the "Renew Link" button still didn't work.

In your screenshot you opened the new invitation link, not the old expired one it seems?

@wing328
Copy link
Copy Markdown
Member

wing328 commented Sep 3, 2025

i tried both (yours and the one in our project's readme)

Screenshot 2025-09-03 150525

@wing328
Copy link
Copy Markdown
Member

wing328 commented Sep 3, 2025

And the "Renew Link" button still didn't work.

did you set it to never expire?

@martin-mfg
Copy link
Copy Markdown
Contributor Author

did you set it to never expire?

Yes. Back some month ago when the link expired for the 1st time and the renew button did work.

I just tried in a private window with the old invitation link as well, and indeed it worked. No idea why I got an error message yesterday evening then that somebody could not join.

Thanks for checking! I guess I can close this PR then.

@martin-mfg martin-mfg closed this Sep 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants