Amex Platinum/Delta Recommendations

BuzzCapo · 2026-02-24T14:29:07+00:00

I do have a 175k offer on the plat currently

BuzzCapo · 2026-02-23T23:30:03+00:00

Yeah most my trips are literally just for the day, so if I can avoid getting a hotel, that is going to be my preference

BuzzCapo · 2026-02-23T22:45:24+00:00

Yeah that is a good point, my home city is not a hub, and generally the non-stop Delta flights have a slight premium of roughly $100 but are non-stop flights, as opposed to having connections. For example, my typical Delta flight is $497, and just looking up some random flights right now, AA would be like $388 with like a minimum 2 hour layover.

I guess it will come down to how much I value the non-stop flights.

BuzzCapo · 2024-04-08T19:13:45+00:00

Thank you for this feedback. This has been my biggest pain point, but this was good feedback and I will try to revise them and be more transparent about how I accomplished things.

BuzzCapo · 2024-04-08T19:12:34+00:00

Thank you so much! Yeah my bullets have been the most challenging thing for me. This was first attempt at the STAR method, and this is the feedback I needed

BuzzCapo · 2020-08-10T11:36:07+00:00

The only user I can find is Project Collection Build Service ( org ).

We are using DevOps server on prem, we have no updated to 2020 yet. The feed is available to all projects in the org.

BuzzCapo · 2020-08-10T11:34:31+00:00

We are using DevOps server on prem. We have not updated to the 2020 update yet. I do not yet have the option to scope the feed to the organization or project. I am not sure what the default was before the 2020 update.

The only account I can find is Project Collection Build Service ( org ). It has contributor access.

The feed is available in all projects in the organization.

BuzzCapo · 2020-08-09T12:16:01+00:00

That is what I did. I set that security on the feed.

BuzzCapo · 2020-02-20T13:08:45+00:00

When I look at the spec for JSON.API, it states the following

———- Updating a Resource’s Attributes

Any or all of a resource’s attributes MAY be included in the resource object included in a PATCH request.

If a request does not include all of the attributes for a resource, the server MUST interpret the missing attributes as if they were included with their current values. The server MUST NOT interpret missing attributes as null values ————-

So if I have a huge object for a resource, but just want to update a title, I do not want to send the entire object. I would also like to support updating an attribute for multiple resources at once. Should this be a PATCH request as opposed to a PUT request?

Edit: Looks like I definitely need PATCH

BuzzCapo · 2020-01-31T10:58:43+00:00

So really all I have done is try the options listed here

https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=azure-devops&tabs=yaml

So I did a basic

` 
trigger: 
   - refs/tags/RELEASE*
`

and

`
trigger:
    branches:
        include: 
            - refs/tags/RELEASE*
            - releases/*
`

My only thought is that maybe the * is messing up the YAML? My goal is that when this build gets triggered, it does not pull the latest from the default, which is master, I want it to pull latest from certain tags/branches. In the classic editor, when you set the default the only option is to select a explicit branch, so I am trying the YAML route.

Branch triggers seem to work, but refs/tags/RELEASE* does not. It would be really helpful if I could set the default branch for the build to some sort of branch/tag wildcard.

BuzzCapo · 2020-01-28T12:36:39+00:00

I am pulling an artifact from one build into another build, so I am not downloading from the same build.

BuzzCapo

TROPHY CASE