Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[C#] chore: Push appsettings file to fix failing build #988

Merged
merged 1 commit into from
Dec 1, 2023

Conversation

singhk97
Copy link
Collaborator

@singhk97 singhk97 commented Dec 1, 2023

Linked issues

closes: #836 (issue number)

Details

06.auth.teamsSSO.bot build was failing due to missing appsettings.Development.json file. Fixed
06.auth.teamsSSO.messageExtension build was failing due to missing appsettings.Development.json file. Fixed

Attestation Checklist

  • My code follows the style guidelines of this project

  • I have checked for/fixed spelling, linting, and other errors

  • I have commented my code for clarity

  • I have made corresponding changes to the documentation (we use TypeDoc to document our code)

  • My changes generate no new warnings

  • I have added tests that validates my changes, and provides sufficient test coverage. I have tested with:

    • Local testing
    • E2E testing in Teams
  • New and existing unit tests pass locally with my changes

@singhk97 singhk97 merged commit 7a63b1f into breaking-changes-2 Dec 1, 2023
5 checks passed
@singhk97 singhk97 deleted the kavin/fix-samples branch December 1, 2023 06:14
singhk97 added a commit that referenced this pull request Dec 6, 2023
## Linked issues

closes: #836  (issue number)

## Details

`06.auth.teamsSSO.bot` build was failing due to missing
`appsettings.Development.json` file. Fixed
`06.auth.teamsSSO.messageExtension` build was failing due to missing
`appsettings.Development.json` file. Fixed

## Attestation Checklist

- [x] My code follows the style guidelines of this project

- I have checked for/fixed spelling, linting, and other errors
- I have commented my code for clarity
- I have made corresponding changes to the documentation (we use
[TypeDoc](https://typedoc.org/) to document our code)
- My changes generate no new warnings
- I have added tests that validates my changes, and provides sufficient
test coverage. I have tested with:
  - Local testing
  - E2E testing in Teams
- New and existing unit tests pass locally with my changes
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.

1 participant