-
Notifications
You must be signed in to change notification settings - Fork 5
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
Fix: Different startup steps implementation since other fix fails to restore #622
Open
Joshua-Lester3
wants to merge
13
commits into
IntelliTect:main
Choose a base branch
from
Joshua-Lester3:StartupSteps
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Joshua-Lester3
had a problem deploying
to
BuildAndUploadImage
October 15, 2024 22:32
— with
GitHub Actions
Failure
Joshua-Lester3
had a problem deploying
to
BuildAndUploadImage
October 16, 2024 15:49
— with
GitHub Actions
Failure
Joshua-Lester3
had a problem deploying
to
BuildAndUploadImage
October 16, 2024 15:52
— with
GitHub Actions
Failure
Restores on my machine - not quite sure why the runner isn't able to. |
Joshua-Lester3
had a problem deploying
to
BuildAndUploadImage
October 16, 2024 15:57
— with
GitHub Actions
Failure
Joshua-Lester3
had a problem deploying
to
BuildAndUploadImage
October 16, 2024 23:29
— with
GitHub Actions
Failure
Joshua-Lester3
had a problem deploying
to
BuildAndUploadImage
October 17, 2024 23:17
— with
GitHub Actions
Failure
BenjaminMichaelis
force-pushed
the
StartupSteps
branch
from
October 22, 2024 23:40
af1c1dd
to
23a3880
Compare
BenjaminMichaelis
had a problem deploying
to
BuildAndUploadImage
October 22, 2024 23:40
— with
GitHub Actions
Failure
Joshua-Lester3
had a problem deploying
to
BuildAndUploadImage
October 23, 2024 16:09
— with
GitHub Actions
Failure
Joshua-Lester3
had a problem deploying
to
BuildAndUploadImage
October 23, 2024 16:10
— with
GitHub Actions
Failure
Joshua-Lester3
had a problem deploying
to
BuildAndUploadImage
October 23, 2024 16:12
— with
GitHub Actions
Failure
Joshua-Lester3
had a problem deploying
to
BuildAndUploadImage
October 23, 2024 16:15
— with
GitHub Actions
Failure
Joshua-Lester3
had a problem deploying
to
BuildAndUploadImage
October 23, 2024 16:57
— with
GitHub Actions
Failure
Joshua-Lester3
had a problem deploying
to
BuildAndUploadImage
October 23, 2024 17:09
— with
GitHub Actions
Failure
Joshua-Lester3
had a problem deploying
to
BuildAndUploadImage
October 23, 2024 17:52
— with
GitHub Actions
Failure
BenjaminMichaelis
force-pushed
the
main
branch
from
October 23, 2024 22:44
59761da
to
d283805
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Pull Request #601 implementation fails to restore. I believe I narrowed the problem down to the added
disabledPackageSources
property in nuget.config, though my access to the Nuget feed isn't currently working.This solution takes the disabling effect out of nuget.config and puts it in the Directory.Packages.props. In the .props file it conditionally restores the private Nuget feed based on the single bool prop,
AccessToNugetFeed
, defined in Directory.Build.props.Credit: GitHub issue 1, GitHub issue 2